On Tue, Nov 09, 2004 at 05:26:29PM -0500, sungo wrote:
> On (11/09 22:13), Markus M?ller wrote:
>
> > Strictly seen, you?re right. The RFC needs \r\n. But you shouldn?t
> > ignore that this RFC is very old.
>
> the tcp spec is old and we still follow it. if the rfc says \r\n, that's
> what you
On Tue, Nov 09, 2004 at 10:13:48PM +0100, Markus M?ller wrote:
> >
> First my important question: How can I use this option with
> POE::Component::Client::Ident ? Could it be that you only have fixed
> POE::Component::Client::Ident::Agent.pm, which have no effect to
> POE:
]
Sent: Tuesday, November 09, 2004 3:57 PM
To: sungo; [EMAIL PROTECTED]
Subject: Re: POE::Component::Client::Ident doesn?t tolerant identd
answers with just \n as line seperator
Hi sungo,
>On (11/09 22:13), Markus M?ller wrote:
>
>>Strictly seen, you?re right. The RFC needs \r\n. But
On (11/10 00:01), Matt S Trout wrote:
> It's a good idea to have a strict mode available, but the default
> should always be to fudge round the error *when it can be done
> unambiguously* - if they send '\n' every time you'd expect '\r\n',
> it's pretty unambiguous that that's what's going on and y
On (11/10 00:57), Markus M?ller wrote:
> If you tell me here that there is no need for to "be tollerant in
> incoming, and strict as possible in outgoing" as I mentionend,
does the IDENT rfc have this clause?
last i saw, the ident rfc only allowed for \r\n terminations. if the
ident rfc allowe
Hi sungo,
On (11/09 22:13), Markus M?ller wrote:
Strictly seen, you?re right. The RFC needs \r\n. But you shouldn?t
ignore that this RFC is very old.
the tcp spec is old and we still follow it. if the rfc says \r\n, that's
what you should send and what you should expect.
you can send "\r\n",
On (11/09 22:13), Markus M?ller wrote:
> Strictly seen, you?re right. The RFC needs \r\n. But you shouldn?t
> ignore that this RFC is very old.
the tcp spec is old and we still follow it. if the rfc says \r\n, that's
what you should send and what you should expect.
--
sungo
http://eekeek.org
bumped up the version to 0.2 and it'll be on CPAN in the next hour or so.
First my important question: How can I use this option with
POE::Component::Client::Ident ? Could it be that you only have fixed
POE::Component::Client::Ident::Agent.pm, which have no effect to
POE::Component::Clie
On Sun, Nov 07, 2004 at 10:09:05PM +0100, Markus M?ller wrote:
> I?ve found a weakness in POE::Component::Client::Ident and accordingly
> POE/Component/Client/Ident/Agent.pm:
>
> It doesn?t support identd answers with just "\n" as line sperator. Only
> "\r\n"
Markus Müller wrote:
Hi again POE Developers,
the file
/usr/lib/perl5/site_perl/5.8.4/POE/Component/Client/Ident/Agent.pm
uses for any error reason the same errorinfo "UKNOWN-ERROR". There is
a subtler differentiation possible and needed: If the socket on port
113 is not opened it is
Hi again POE Developers,
the file
/usr/lib/perl5/site_perl/5.8.4/POE/Component/Client/Ident/Agent.pm uses
for any error reason the same errorinfo "UKNOWN-ERROR". There is a
subtler differentiation possible and needed: If the socket on port 113
is not opened it is a totally errorcond
Hi POE Developers,
I´ve found a weakness in POE::Component::Client::Ident and accordingly
POE/Component/Client/Ident/Agent.pm:
It doesn´t support identd answers with just "\n" as line sperator. Only
"\r\n" is supported. Example:
33 34 30 34 2c 20 35 38 31 32 31
12 matches
Mail list logo
