On Feb 20, 2006, at 21:01, lanas wrote:
2) TCPServ.pm
use POE::Filter::Stream;
use POE qw(Component::Server::TCP);
POE::Component::Server::TCP-new (
Alias = 'bambi',
[...]
3) Supervisor.pm --
sub doStart
{
$_[KERNEL]-post('log1', 'log',
On Feb 14, 2006, at 19:07, lanas wrote:
Using POE::Component::Client::TCP, I'm trying to get some 32
bytes of
data from a process. It goes like this. I send a command code, the
other guy gets it, and then replies with 32 bytes of data. So far so
good. Ethereal shows what's going on.
On Feb 2, 2006, at 18:26, Dan McCormick wrote:
Any objections to adding a check for bad params in Client::TCP? It
would've
saved me some recent typo-related head-scratching. I just stole
the code
from Server::TCP.
[patch]
Patch applied. Thanks!
--
Rocco Caputo - [EMAIL PROTECTED]
On Tue, 21 Feb 2006 11:33:39 -0500
Rocco Caputo [EMAIL PROTECTED] wrote:
Why is this so ? Isn't the alias for TCPServ 'bambi' and isn't it
registered ?
bambi is the alias of the server itself, not that of a particular
connection. Each session runs in a separate POE::Session, so each
Lanas,
The alias bambi is on the server component NOT the sessions it spawns for
each connection. InlineStates don't apply to the main server session but
the child sessions that are created. So your post is going to the server
component, not the child session. This makes sense to me. I
On Tue, 21 Feb 2006 17:34:16 -0800
David Davis [EMAIL PROTECTED] wrote:
The alias bambi is on the server component NOT the sessions it spawns
for each connection. InlineStates don't apply to the main server
session but the child sessions that are created. So your post is
going to the server