Real-time updates demo

real-time PUSH for browsers. reduces overhead of HTTP and with that lowers server load and content load times by a significant amount. source code is included.

 

Isn't that already done with AJAX? I'm not a programmer but from the ones I've talked to that's what I've understood. I know Yahoo and Google's services push without polling using AJAX at least.

 

I'm not quite smart enough to understand what you have done (But I'm interested). I think most current "AJAX" apps use some kind of "long pull" technique -- e.g. they keep a request from the browser open for a long period of time, waiting for something to come down the pipe from the server. This can have a similar effect as a "push", although it is not.

So, does your solution depend on a Flash plugin? I guess I have to read about "Flash TCP Sockets".

Chris (VB Dinosaur)

 

yes, but its very inefficient because request just sits there taking up open apache nodes. on top of that there is a very nasty overhead of http which adds sometimes useless headers that you shouldnt even care about in this scenario. with my approach i removed http completely (except for loading initial page of course) but unfortunately it does rely on flash sockets so this wont work on mobile browsers :(

next week i will be implementing secure sockets (either ssl or tls)

 

That is indeed cool. As a software programmer in a previous life, I can appreciate it.

 

thank you

 

by the way, just did benchmark... my server (2.4ghz core 2 duo, 2gb ram, 250gb raid 5 sata, intel 1gbps network card) maxed out with 985,564 concurrent connections sending packets back and forth constantly! memory was as 55%, cpu was at 40% on one core and 70% on second core, and i had to stop because network card maxed out.

in my next release i want to have ability to load-balance and fail-over servers and have ssl sockets for secure connection.

also, i have another project in the making - low-cost highly-available load balancer which will let you load balance and cluster databases (mysql/postgresql/mssql) and web servers (probably based on nginx). its currently in pre-alpha but i do have some working code for database balancing and replication. in actual release i plan on having file server balancing and replication as well. still debating on what exactly i should use as transfer protocol... was thinking nfs.