I just realized I pushed some Chrome-specific code to the demo server.
 I've revised it, so the demo should now run correctly in up-to-date
Firefox and Chrome.  I don't have access to a Windows machine right now, so
I can't test in IE.  I have no excuse for not testing in Opera, though.

Socket.io uses the best possible connection channel available in the
browser (Websockets, then Flash sockets, then long-poll), so it should use
Websockets automatically if they're available.  However, anything less than
a Websocket connection will be far too slow to be playable, so perhaps I
should just switch to ws.  I'll run some tests and see what the best option


I did indeed lift the architecture of the networking code directly from
Gytha.  I was fortunate that there is a Javascript implementation of the
Python struct packing library, so I needed to change very little.  For the
SP_ and CP_ message objects, I actually wrote a regular expression that
rewrites the Python code into Javascript syntax.  (I'll be sure to mention
you in my copyright docs as soon as I put up a license on the Git repo!)

Thanks again for your advice and very readable Gytha code.  I definitely
wouldn't be nearly as far as I am without it!

I'll send out another notice when I've improved the cosmetics, done some
performance improvements, and added a feature or two (chat and
army transportation are high on the list).


On Wed, Apr 4, 2012 at 5:09 AM, James Cameron <quozl at us.netrek.org> wrote:

> I've reviewde the code in git, I like it, well done.  I see how it
> derives from some of my work on Gytha.
> I'm interested in hearing more, do keep us informed.
> --
> James Cameron
> http://quozl.linux.org.au/
> _______________________________________________
> netrek-dev mailing list
> netrek-dev at us.netrek.org
> http://mailman.us.netrek.org/mailman/listinfo/netrek-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.us.netrek.org/pipermail/netrek-dev/attachments/20120404/2647113e/attachment.html>