GUIs - ruby on rails, rico

[David Hopwood]

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.

This will be handled badly by most TCP/IP implementations, even if Erlang
and the web server do everything right.

-- 
David Hopwood <david.nospam.hopwood@REDACTED>