Re: POE message not sent or received

2006-03-11 Thread Rocco Caputo
On Feb 25, 2006, at 19:27, lanas wrote: Is it possible to assign specific subroutines to connections in the view of perhaps generating on-the-fly specialized subroutines depending on a connection attributes ? You can use POE::Kernel's state() method to redefine event handlers at runtime.

Re: POE message not sent or received

2006-02-25 Thread Rocco Caputo
On Feb 25, 2006, at 10:43, lanas wrote: Rocco Caputo [EMAIL PROTECTED] wrote: {Inline,Object,Package}States apply to each connection session, not the main server session for the component. You can certainly send arbitrary messages to the server session, but it will not handle them. Is

Re: POE message not sent or received

2006-02-25 Thread lanas
On Sat, 25 Feb 2006 11:45:36 -0600 Matt Sickler [EMAIL PROTECTED] wrote: Hi, What is it that your trying to accomplish? This will help us suggest what to use. It's a middleman between a source of data and a requester of data. Both of these being already existing entities using TCP. The

Re: POE message not sent or received

2006-02-25 Thread lanas
On Sat, 25 Feb 2006 12:39:20 -0500 Rocco Caputo [EMAIL PROTECTED] wrote: Hi, Would it be otherwise possible, by using a Socket Factory and a R/W Wheel instead of a component ? Would two servers built like this be able to communicate to each other using POE messages targeted at their

Re: POE message not sent or received

2006-02-25 Thread lanas
On Sat, 25 Feb 2006 12:39:20 -0500 Rocco Caputo [EMAIL PROTECTED] wrote: Rocco, It would be more efficient to address the client connection's session directly rather than bounce your messages off POE::Component::Server::TCP's main listening session. Got it, finally. Now's the time to play

Re: POE message not sent or received

2006-02-23 Thread Rocco Caputo
On Feb 21, 2006, at 21:00, lanas wrote: 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

Re: POE message not sent or received

2006-02-21 Thread Rocco Caputo
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',

Re: POE message not sent or received

2006-02-21 Thread lanas
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

Re: POE message not sent or received

2006-02-21 Thread David Davis
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

Re: POE message not sent or received

2006-02-21 Thread lanas
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

POE message not sent or received

2006-02-20 Thread lanas
Hi all, A POE message is not received by a Component and I don't see why since it follows the same route and definition, or it seems, as one that is successfully sent and received. Here's the context: A main program uses 3 modules and starts the POE kernel. In sequence: The first module is a