Another massively important geek tool
Dec. 3rd, 2007 09:41 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
elfsAlong with Pound and Merb, I found another very important geek toy this weekend: Juggernaut. Juggernaut is going to absolutely change the way the web works, and it's going to do it frigteningly fast. Because Juggernaut destroys the one major complaint we developers have about the web: it's statelessness.
Juggernaut creates a little javascript applet (not java, javascript) on the browser with a permanent TCP/IP connection to the server. Through this connection, it is possible for the server to send events to the client without being polled.
If you have no idea how important that is, don't worry about it. To those of us for whom time-critical events are just that, critical, it makes all the difference. Now, instead of constantly harassing the server and being out-of-date within seconds of the poll, you get real-time data from the server when the server thinks it's significant. It pulls the web into the 20th century: no more busy-waiting, no more collate-without-effect.
Now if only I had something that had a use for it.
Juggernaut creates a little javascript applet (not java, javascript) on the browser with a permanent TCP/IP connection to the server. Through this connection, it is possible for the server to send events to the client without being polled.
If you have no idea how important that is, don't worry about it. To those of us for whom time-critical events are just that, critical, it makes all the difference. Now, instead of constantly harassing the server and being out-of-date within seconds of the poll, you get real-time data from the server when the server thinks it's significant. It pulls the web into the 20th century: no more busy-waiting, no more collate-without-effect.
Now if only I had something that had a use for it.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2007-12-04 07:52 am (UTC)But there are going to be effects on the TCP/IP stack the server uses. Less overhead making and breaking connections, but more resources tied up by connections. Less CPU time, more memory use, perhsps.
To my untutored eye it looks to shift some of the problems from people at your level to the people who have to deal with the actual details of the internet.
The winnage may not be evenly distributed.