GUIs - ruby on rails, rico

[Mickael Remond]

Richard Cameron wrote:
> So, of course, the hacky bit is trying to turn the HTTP "pull"  protocol 
> into a "push" protocol by having the browser spending all  its time 
> sitting with an open socket on port 80 waiting for the  server to return 
> the next message. Having several thousand open  sockets (one for each 
> connected client) at once is the sort of thing  which would utterly kill 
> any apache based server infrastructure, but  the Yaws propaganda 
> <http://www.sics.se/~joe/apachevsyaws.html>,  support for /dev/poll and 
> kqueue in Erlang on certain architectures,  and the whole design of 
> Erlang/OTP indicates that it's probably the  right tool for this hack.

That's what I am pushing with J-EAI, ejabberd and out Instant messaging 
stuff. If you replace HTTP with a bidrectionnal connected protocol you 
can have realtime feedback from the server in your application. This is 
how instant messaging application work and this is how you could define 
enhanced clients that keep the connection with the server, exchanging 
data in both direction. The XMPP protocol is quite nice for that.

-- 
Mickaël Rémond