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

[Erik V. <eri...@hc...>]

 

> -----Original Message-----
> From: rai...@li... 
> [mailto:rai...@li...] On Behalf 
> Of brett lentz
> Sent: Thursday 07 August 2008 21:35
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] [18xx] Rails (was: Web-based 18xx)
> 
> On Thu, Aug 7, 2008 at 1:07 PM, Erik Vos <eri...@hc...> wrote:
> > What we need for "real" real-time play is some API that 
> can, both on the
> > server and the client side, take a Java object (or a series 

> If we use XMPP, the server-side would be just another jabber server,
> and people could use any jabber server they want.  This has some
> advantages, because we can then leverage things like Jabber.org and
> google talk as ways of connecting our clients.

OK, so the game engine (acting as the GM) will also be a jabber client.
 
> However, doing a "basic" client/server application is relatively
> simple:  http://williams.comp.ncat.edu/Networks/JavaSocketExample.htm

Yes, I know. A while ago I have developed a fairly elaborate comms package
based on such principles.
In fact I have in mind to reuse it here in some form. 
But then the game enogine will be a server listening to some port, open to
everyone.
That's fine on a LAN, but is this secure enough for the Internet, even with
basic authentication? I doubt.
 
> > In any case: I don't want another batik.
> >
> 
> I'm not sure I understand what you're referring to there.

Its enormous size - and so many libraries that call each other and that all
need to be mentioned in the classpath....