i plan to write a little irc proxy which breaks up the join/part messages and rebuilds them in a form mschat can handle probabablly stripping out the reason part completely and sending all join/part messages on to mschat in the form :sender join #channel
anyway rfc1459 is known wrong in some parts rpl-inviting for example and it only claims to be a draft. NOWHERE in rfc1459 is it claimed that rfc1459 is the definitive standard for irc
From: bas <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: RE : [Coder-Com] Fwd: [Cservice] accessability enquiry
Date: Mon, 31 Mar 2003 13:41:41 +0200
MIME-Version: 1.0
Received: from mc6-f37.law1.hotmail.com ([65.54.252.173]) by mc6-s14.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon, 31 Mar 2003 03:58:43 -0800
Received: from trek.sbg.org ([66.218.53.89]) by mc6-f37.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon, 31 Mar 2003 03:58:43 -0800
Received: (from [EMAIL PROTECTED])by trek.sbg.org (8.12.8/8.12.7) id h2VBXQ9X023541for coder-com-outgoing; Mon, 31 Mar 2003 03:33:26 -0800
Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138])by trek.sbg.org (8.12.8/8.12.7) with ESMTP id h2VBXLE3023537for <[EMAIL PROTECTED]>; Mon, 31 Mar 2003 03:33:21 -0800
Received: from xs4all.nl (beware.xs4all.nl [80.126.79.169])by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id h2VBffQX091896for <[EMAIL PROTECTED]>; Mon, 31 Mar 2003 13:41:42 +0200 (CEST)
X-Message-Info: 0jbW5ANosZKhuDT1KCp1o5VczeOfJasU
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
References: <[EMAIL PROTECTED]>
X-Scanned-By: MIMEDefang 2.29 (www . roaringpenguin . com / mimedefang)
Sender: [EMAIL PROTECTED]
Precedence: bulk
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 31 Mar 2003 11:58:43.0204 (UTC) FILETIME=[E05DBC40:01C2F77C]
peter green wrote:
>
> ok tonight i'll try to code a sanitiseing proxy, mscaht connects to
> localhost my program connects on to the irc server then the program will
> parse the traffic flowing from the irc server back to mschat and rebuild it
> in a form mschat can handle
>
> >
> > > This basically means you end up having to special case this (is there a
> > > colon? Then theres no part message. Is there no colon? Then theres a
> >part
> > > message) which seems to be nothing but extra work.
> >
> >Huh? You're confused. The RFC says that if there's a :, then all text
> >following the colon, even field separators (white space), is part of the
> >final argument. In other words, : is a sentinel for the last argument
> >in a command.
> >
> > > And theres exactly the same `issue' for clients rejoining during a split
> >-
> > > I forget which way around it is but a normal client join and a netsplit
> > > join are different - one is : prefixed, the other is not.
> >
> >*sigh* not too surprising--they're generated by different routines in
> >the source. I hope to be able to consolidate these in the future.
> >--
> >Kevin L. Mitchell <[EMAIL PROTECTED]>
> >
plugwash clearly doesn't understand the RFC, and thinks about it in the same broken way as some client coders. "a b :c" == "a b c" and means: 3 tokens, "a", "b", "c". interpreting it in any different way is wrong.
beware
_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger
