Re: [Rails-devel] [18xx] Rails (was: Web-based 18xx)

[Dave M. <da...@mi...>]

On 8/6/2008 06:30 PM, Erik Vos wrote:
> > If we want to leverage some existing code, for the "near realtime"
> > communication, XMPP (aka. Jabber) is a more appropriate protocol. I
> > believe there are a few different existing libraries we can leverage
> > for the communications, which could save us a TON of work.
>
>XML simple? It's verbose and slow, and needs lots of code to build and
>parse, as I have experienced so far...   Its main asset is that it's
>readable (and, oh yes, fashionable).
>
>The simplest thing IMO would be to pass on serialized java objects.
>Save/Load is already based on (de)serialization. It's simple and fast and it
>works.
>
>My question is rather how to transfer such serialized objects between client
>and server, or applet and server, or whatever.
>
>...
>
>Erik.

I don't know what other mechanisms have been considered, but
Sun's JINI can pass objects. and deal with the clienr/server issues.

I spent a few months trying to learn it but gave up when other 
opportunities arose.
It tapped into a lot of heavy weight distributed communication 
features that I recognized their value from my software development 
experience, but found a bit daunting to learn all at once in a new platform.

It's more of a framework than a package.

FWIW...

Dave.