Don, you might consider Node.js plus Socket.io. Socket.io uses websockets for maximum performance but can fall back to a range of legacy technologies for browsers that can't do websockets. All transparent to the application programmer.
On Fri, Dec 30, 2011 at 8:34 AM, Folkert van Heusden <[email protected] > wrote: > Hi Don, > > > That sounds pretty appealing. We have a theory that RAM is the > problem > > due to disk caching so that is an appealing solution. I'm not sure how > > much is allocated to the boardspace server but I think it's pretty small. > > What do you do with this VPS? > > Currently mostly nothing. Well, 2 low volume websites but that's about it. > > > I do plan to upgrade the software and provide a much nicer web based > > websockets interface. I have been delaying because websockets are not > quite > > there yet, but it's going to be big. In this way you will be able to > > interactively watch one or more games being played. I already have a > good > > part of the code written in C so that it will be resource friendly and > > figured out how to do stuff without using sql which is a resource hog. > > Do you have an html5 enabled web server or can you install one so that I > > will have websockets? > > It currently has Apache 2.2.21 running on a Debian distribution (linux > kernel). > Running an other webserver is possible, but that would be on a > different port then. > If you want I can give you a shell account (ssh) so that you can nose > around to see if it fits needs? > > > Folkert. > _______________________________________________ > Computer-go mailing list > [email protected] > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go >
_______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
