Ok, but what about the responses?
On 6/17/07, Keith Hodges keith_hodges@yahoo.co.uk wrote:
Chris Muller wrote:
I have made it fairly generic since it passes arbitrary messages, and returns any values, trapping server-side errors, it transports them back over the wire in order to signal them in the client.
"Ma client server" does not support a dynamic protocol; only fixed which must be established just before session negotiation. How do you handle this?
My MagmaServerRequest being a subclass of RepositoryRequest is registered as part of the Magma protocol as you say. It has an attribute 'requests'. This is passed as an Array of Message' instances, both of these appear to be understood by Magma for serialization. At the other end I check that the Message-#selector's are defined in the #requestsSupported and simply send them to the class that implements that selector.
cheers
Keith
Setools mailing list Setools@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/setools
Chris Muller wrote:
Ok, but what about the responses?
Ok, so I was wrong to say "arbitrary",
I discovered that 'Error' instances, and Messages work, and Arrays, Dictionaries, Strings, Numbers all go accross the wire just as is. So I figured that there were enough datatypes already supported to be useful.
I am still looking for MutatingProxyStandin since I accidentally loaded a package over it!
Keith
magma@lists.squeakfoundation.org