I wouldn't run a long running process directly from your controller,
since rails first renders all stuff that should be sent to the client
(html/xml/js/etc) before it actually sends it. This means that the
complete controller action should be finished to show something in your
browser.
I
Wouter de Bie wrote:
I wouldn't run a long running process directly from your controller,
since rails first renders all stuff that should be sent to the client
(html/xml/js/etc) before it actually sends it. This means that the
complete controller action should be finished to show something
I don't think multiple processes can access the same Hash. Multiple
threads should be able to do this. Maybe a dirty solution is to use the
database for this and do pessimistic locking on a record.
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
3 matches
Mail list logo