I've done a little more digging and now I'm really confused.
Consider the following '_stop' handler for a Client::Ping session.
sub handler_stop {
print Session , $_[SESSION]-ID, has stopped.\n;
print $poe_kernel-get_active_event() . - .
$poe_kernel-get_event_count() . \n;
On Feb 21, 2007, at 15:05, Kevin Scaldeferri wrote:
I'm trying to figure out how to schedule an action to happen after
my PoCo::Server::TCP shuts down. I.e., after all the pending
requests have finished processing. I tried doing it through _stop
like this, but it didn't work:
On Feb 22, 2007, at 01:52, Michael Collins wrote:
I am searching for a way to catch and handle a Control-C when using
multiple POE sessions. I have successfully used the snippet from
the POE
Cookbook to actually catch the INT signal in each of my Sessions:
event_sigint = sub {
my
On Feb 13, 2007, at 18:59, Paul Miller wrote:
On Feb 13, 4:04 pm, [EMAIL PROTECTED] (David Davis) wrote:
POE .95
Perl v5.8.7
Oh, and I suppose I failed to mention that part. I'm running perl
v5.8.8 and POE 0.9917.
I can't reproduce the output truncation. I'm running the sample code
Forgot the list... sorry.
-jp
-- Forwarded message --
From: Jake Peavy [EMAIL PROTECTED]
Date: Feb 21, 2007 6:09 PM
Subject: Re: EasyDBI -- No result, just 'Died' [Was: POE DBI]
To: David Davis [EMAIL PROTECTED]
I'm not totally sure what you mean by error message...
With
sub
Hi group, just wondering what's the difference between
POE::Kernel::select_read/write method and POE::Kernel::yield method? How
should I use select_read/select_write? Do they do anything special about
the events that they select? Thanks,
Fei
Since I don't have a test case, You'll have to dig deeper yourself.
David
On 2/22/07, Jake Peavy [EMAIL PROTECTED] wrote:
Forgot the list... sorry.
-jp
-- Forwarded message --
From: Jake Peavy [EMAIL PROTECTED]
Date: Feb 21, 2007 6:09 PM
Subject: Re: EasyDBI -- No result,
Sure, I don't mind, but how would you suggest doing so? Like I mentioned in
the OP, the queries run without problems through straight DBI (using the
same DBD::ODBC driver).
-jp
On 2/22/07, David Davis [EMAIL PROTECTED] wrote:
Since I don't have a test case, You'll have to dig deeper