Hi!
I have a legacy service sending data (well, messages to be delivered to the
client) through a TCP socket. I need to deliver those messages to the
browser, likely through periodical ajax updates (I''ll adapt the
frequency
between visual comfort and server load).
I''d be interested to hear from people who have implemented something
similar
already.
I have various roads in minds, like:
- a stateful ruby app doing the polling, and exposing data through dRB
- same app, but storing the messages in a database queue (AR)
- yet same app, but relying on ruby spread or another messaging system to
have the messages delivered
(btw, did you notice I didn''t even mention the word
''container'' ? :-)
What do you think ?
Thibaut
--
[blog] http://www.dotnetguru2.org/tbarrere
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060505/ef00ad14/attachment.html
