Home
Joel Liu's Library tagged → View Popular, Search in Google
-
I made this RPG node demo a while back: http://sleeperbot.com
I'm not using any server monitoring so it can crash at any moment.
Would love to get more than 15 users on here moving around and see what happens.
-
Regardless of the popularity of Javascript on the server-side, if you're writing a web-based application, then your architecture will benefit from:
1. Shared code between client and server.
2. Specialization in one language.
V8 and Node are at least a very good combination for server-side Javascript.
Re: "is it absolutely not suitable for production use?"
Node in alpha state is already more production ready than many "production ready" tools.
-
Taskforce uses a synchronization framework called Syncro which relies on a open socket connection to the server. We're using WebSockets on Chrome and Safari, so that would be the logical option for the iPhone. However, annoyingly Apple decided to disable WebSockets in iOS 4. What's strange was that WebSocket support was in all the previous development releases - oh well...
So, how can we keep a open socket connection to the server from a Mobile Safari webpage? The answer is long polling - i.e. you open an AJAX connection to the server, and never close it. It's one way only though, so if you want to send any data to the server, you need to send a separate AJAX POST. It's all fairly ugly, and hopefully something we can do away with once the majority of devices support WebSockets.
-
WebSocket is "TCP for the Web," a next-generation full-duplex communication technology for web applications being standardized as a part of Web Applications 1.0. The WebSocket protocol is more efficient than HTTP as used in Ajax, so it is more suitable for real time and dynamic web applications. WebSocket also provides a very simple API that can be used to communicate bidirectionally between the web browser and a server, so it makes it easy to develop such web apps.
-
Developers should be aware that starting from WebKit nightly build r59903 and Chrome 6.0.414.0 (r47952), the client will talk to a server using -76 version of the protocol, so it will fail to open WebSocket connections with a WebSocket server based on draft-hixie-thewebsocketprotocol-75. Since -75 version of the protocol is obsoleted and no longer supported in future version of browsers, to support new clients you need to update the server implementation. (Note that Chrome 5 uses -75 version of protocol).The WebSocket protocol is still actively being changed. Until there is more consensus, we will continue to update our implementation to follow the latest draft of specification, rather than worrying about breaking changes.
Top Contributors
Groups interested in WebSocket
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo