Juggernaut, Push Server, The future of the web

My dear blog, it's been 3 long month since my last post. Forgive me.
I had so many stuff to do:

• Coding - have you seen the new forums at SA? (http://seekingalpha.com/symbol/aapl/mb/topics)
  Kudos to everyone in SA tech team
  
• Running
• Learning Italian
• A little more ...

But than - suddenly, unexpectedly, I ran across... The next hottest thing in WEB - JUGGERNAUT!

Yes, treat it as the new Gospel in our business... web.

1. What is it?
2. What's new? we had it since ever!
3. How will it change the web?
4. How can I start?

1. What is it?

It's more than Ajax.
Ajax is an HTTP connection that's opened especially per request and closes as it ends.
Juggernaut, with Flash OBJECT on the Client Side and Ruby Server (Push Server) on the Server Side, allows you to keep an open connection and thus allow real-time connection.



YU HU!!! what's so amazing about it???

Very high frequency (on my machine ~ 2000 req/second)
Scalability (based on EventMachine)
Low Hosting Costs (less servers and memory is needed than if Ajax was used)

2. What's new? we had it since ever!

Juggernaut does it well, easy, cheap and smart.

Client Side: JavaScript + Flash Object
Server Side: Ruby

3. How will it change the web?

Chat is nice but think of all the collaboration and real-time data services you know, think of it functioning 10x faster.

4. How can I start?

Luckily, Juggernaut code is updated very frequently - improvements are made and bugs are being treated.

Unfortunately, it changed it's already somewhat known API and so the already written tutorials are obsolete.

Luckily, I am going to explain how to get this sweety to work in my next post:

http://www.dorkalev.com/2008/04/juggernaut-up-to-date-tutorial-1042008.html

Kudos to Alex MacCaw from http://www.eribium.org/ for creating and maintaining Juggernaut