On Wednesday 01 May 2002 03:05 am, you wrote:
> At 02:57 AM 5/1/2002 -0400, Peter Chen wrote:
> >What is the convention for handling daemonization in a POE application?
>
> I am unsure how kosher this solution is, but it's "functional" as far as I
> know. I jacked the daemonize() routine out of p
At 02:57 AM 5/1/2002 -0400, Peter Chen wrote:
>What is the convention for handling daemonization in a POE application?
I am unsure how kosher this solution is, but it's "functional" as far as I
know. I jacked the daemonize() routine out of perlfaq and called it just
before $poe_kernel->run();
What is the convention for handling daemonization in a POE application?
In particular, what I am wondering is whether typically one daemonizes
before $poe_kernel->run() or do the daemonization in one of the
"application manager" sessions.
For example, I am considering using what I call a "StoreK
On 24-Apr-2002 Dan McCormick wrote:
> Hi,
>
> Does anyone have any advice for writing a POE object/session in such a
> way that the main program doesn't need to know all its states?
>
> The problem is that if you write 20 programs that use one POE
> object/session, and then add an internal, pri
On Tue, 30 Apr 2002 16:34:24 -0400 Rocco Caputo wrote:
+--
| Just verifying that the list itself is still up, what with it being
| quiet and all. :)
+--
Here is an ack for your syn.
--
14:41 Stange, I can't register to the mailing list.
14:41 EZMLM does not return me mails
Just verifying that the list itself is still up, what with it being
quiet and all. :)
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sf.net
