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
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 suggest
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, s
On Tue, 21 Feb 2006 12:03:41 -0500
Rocco Caputo <[EMAIL PROTECTED]> wrote:
Hi,
> > Client 2 got read error 0 (Normal disconnection)
> > The ServerInput event never gets the data.
> It sounds like the server is sending back a block of binary data,
> not a CR/LF terminated line. You may want to
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 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. But
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', "Sup
I cannot get concurrency to work. I want to get the new feature below to
work:
Concurrency => $MAX_CONCURENCY
My Server::TCP component works great when $MAX_CONCURRENCY is -1
(unlimited), but when I set $MAX_CONCURRENCY to 3, I can only make 3
connections and then everything fails
