Catalyst::Engine needs a stop method

Hi Kennedy,

Thanks for the suggestion.  Although it's a possible option
for me, it's
not my preference.  Before forking, I set up the context for
the
background operation in the Cat environment, so I would have
to
reproduce all of that logic separately if I were to use a
separate POE
server.

-- 

Jon


On Fri, 2006-10-27 at 21:19 -0400, hkclarkgmail.com
wrote:
> On 10/27/06, Jon <jon+catalystyouramigo.com> 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.
> 
> Regards,
> Kennedy
> 
> _______________________________________________
> List: Catalystlists.rawmode.org
> Listinfo: ht
tp://lists.rawmode.org/mailman/listinfo/catalyst
> Searchable archive: http://www.mail-
archive.com/catalystlists.rawmode.org/
> Dev site: http://dev.catalyst.per
l.org/

_______________________________________________
List: Catalystlists.rawmode.org
Listinfo: ht
tp://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-
archive.com/catalystlists.rawmode.org/
Dev site: http://dev.catalyst.per
l.org/