On Jun 9, 2009, at 11:08 AM, John Huss wrote:

I believe JavaClient uses the standard Java serialization, which is a binary format. Generating the format in Javascript is probably not feasible; if it was I'm sure the GWT folks would have used it, but they didn't.

Hmmm. I wonder if it would be possible to get Apple to add the serialization methods to the EODistributionContext.Delegate interface so that you could pick something like JSON instead...

Also, JavaClient's serialization is HEAVY since the whole EC is transferred (I think) with each request to the server,which kind of makes sense actually, but is possibly an expensive operation.

Yeah. It would be heavy. I'm thinking though that as more and more devs start having to deal with manually specifying and transferring all the various EOs that they'll need to be able to make a truly rich interface, that in the end, simply transferring the EC will be best in most situations. Especially if you are using page-specific ECs.

You certainly have a valid point about the large amount of data transferred between a rich client and the server, but in most cases you are greatly reducing the number of client-server transactions required to accomplish a given task.

Also, you would have to rewrite EOEditingContext and related classes in Javascript, which is a fairly large task.

But I thought that was part of what Gianduia did and what made it so much cooler than last years rich-client-of-the-moment Sprout Core.

Dave


John

On Tue, Jun 9, 2009 at 9:57 AM, David Avendasora <[email protected] > wrote:
Hi all,

I have a question that I think I can finally put into words after an excellent WOWODC, especially the session on Javascript Clients.

Why not use the already built-in com.webobjects.eodistribution classes as the interface for passing EOs and such back and forth instead of re-inventing the wheel? This is how a JavaClient application passes EOs and ECs back and forth between the client and server, and the default method is HTTP using POST commands. Couldn't a Javascript client simply leverage that existing interface to the server-side EOF stack?

Dave

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/johnthuss%40gmail.com

This email sent to [email protected]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to