On 08 Dec 2010, at 13:37, Frederick Cheung wrote:
On Dec 8, 11:35 am, Fearless Fool <[email protected]> wrote:
My first instinct is to spawn a thread to run the process, and use a
carefully managed interface to provide updates. But I suspect that
may
not work the way I expect -- it really depends on the lifecycle of
ActionPack transactions, no? (For example, would I need do a join
somewhere to keep the owning process alive long enough for the
thread to
complete?)
Look at something like delayed_job..
Or Nanite combined with Redis for the progress feedback.
Also, instead of using a periodical updater you could look into a push
server (and event-based server like Node.js to send the events on the
server, some websockets+fallback script on the client side).
Best regards
Peter De Berdt
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
