[EMAIL PROTECTED] wrote:
On 10/27/06, Jon <[EMAIL PROTECTED]> wrote:
I need to launch a long-running (minutes up to hours) background program
from Catalyst. I have it working almost well enough - I do the usual
double-fork, closing standard file descriptors, and had to take some
particular care to use POSIX::_exit and put an eval{} around the daemon
code so that if it dies it doesn't return to the Catalyst main loop -
and it runs, exits cleanly and doesn't interfere with other Catalyst
operations.
Hi Jon,
I know this probably isn't the answer you are looking for, but when I
discussed a similar requirement on IRC, they convinced me to write a
POE job server. I was surprised how easy it was and how well it
works. I'm using POE::Component::Server::XMLRPC.
And Catalyst::Engine::JobQueue::POE is being developed in trunk atm.
However, I'd love to see a proper RFC for an Engine stop method on
catalyst-dev so we can have a proper discussion about it.
--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
