Back story While coding I've stumbled upon many problems with creating rich multiplayer web-based games. Some of them exist because the communication supported by browsers is not really game-friendly. The HTTP protocol is inherently stateless, so some overhead is required to keep sessions using cookies and whatnot. Each communication requires a new connection, raising lag.

Base Wars Gamenode Download Music. The skill game Raft Wars is a funny action version of Battleships! Get ready to play the most exciting action games! Play free online war games, strategy games, bomb it games and tower defense games. Free Online War Games.

Servers cannot push data to clients, because the system was designed for request-based applications, like web pages mostly are. The ones more experienced with web programming are now thinking: 'you can get around all that using long polling/comet/whatever!' Yes, but most web servers are not really up to the task of serving a huge amount of long-polling clients.

Most assume only a handful of concurrent connections with short lifespans. They are not suitable for long-lived connections. In addition, long polling techniques have their own set of disadvantages, such as missing data when reconnecting and http overhead and difficulties in communication between clients. Now I imagine some of you think 'Well, I can use a publish-subscribe messaging server such as for the data pushing!' , but those bring a whole bunch of other problems, like separate logins for the web content and game data server.

This is how we currently do things in Wars, and I got to thinking that there must be a nicer way. A nice, clean socket connection to a backend server. Although it's currently having some, it is in my opinion the future of any two-way communication in web applications. This got me thinking: what if ALL dynamic data for an application was available only through a websocket server, and all html/css/js was served as static files. The Berry Patch Campbellsville Ky on this page. This means no server-side generation of HTML, only static files and a websocket to fill the page with data. A nice clean separation between the view and the model.

This model also solves the login issue, because one only needs to log into the web socket interface. The static pages are only templates, so getting them won't gain you anything. After tinkering with this idea for a while I noticed that if the login happens through a websocket, I of course cannot switch pages without losing my session. First I thought about creating a small view framework to keep the user actually on the same page and only dynamically modify the DOM to show different views. This idea was short-lived, because I wanted direct support for nice URL based navigation and back button and so on.

So back to the drawing board. Next I thought about the current common implementation using cookies to send a session ID with each request. I didn't want cookies to have anything to do with my framework, but that reminded me of an interesting HTML5 feature: or more accurately the SessionStorage part of it. This allowed me to store the session ID to the browser after successful login, and use it to restore my session after loading each page. Now I had something I could use.