On Sep 15, 2005, at 0:58, Andrus Adamchik wrote:
> Not Cayenne features per se. Serialization mechanism is outside of
> the scope of the Cayenne client/server communication "protocol"
> that only defines what messages server can process and what objects
> it would send in reply.
Ok, that makes sense.
> But serialization mechanism choice would affect deployment. If we
> use XML, client can be anything - Java, .NET, etc. Encoding can be
> done in generic form... If we use Java serialization on the other
> hand (or Hessian variety which is part custom, part Java), two
> communicating JVMs would have to access the same set of classes,
> hence - client classes would have to be available on the server.
I was thinking about a objective-c/cocoa client framework. That would
have been cool (for the mac-users).
- Tore.
This archive was generated by hypermail 2.0.0 : Thu Sep 15 2005 - 02:52:43 EDT