[dcc2] DCC Chat suggestions

peter green plugwash at p10link.net
Sat May 22 11:07:31 EDT 2004


a normal ctcp has both the first and last char as #1

how about in dcc2 cpcps using the last char to differentiate between
requests and replys

-----Original Message-----
From: dcc2-bounces at dcc2.org [mailto:dcc2-bounces at dcc2.org]On Behalf Of
Jesse McGrew
Sent: 22 May 2004 15:35
To: DCC2 Working Group List
Subject: Re: [dcc2] DCC Chat suggestions


Szymon Stefanek wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Saturday 22 May 2004 05:17, Jesse McGrew wrote:
>
>
>>Since we can't distinguish between CTCP requests and responses over DCC
>>Chat as we can over IRC, I'd suggest using a different name for the
>>response, so client authors don't have to worry about infinite loops.
>>PING/PONG, perhaps.
>>
>>
>
>I suggest using a different CTCP tag character for queries and replies.
0x01
>can be used for queries and 0x02 for replies, for example.
>
>
Well, 0x02 is bold, 0x03 is kholour, 0x04 is RGB color... there are many
free codes, but I'm reluctant to assign a new control character that
will only be meaningful in DCC Chat.

We could use a naming convention to distinguish CTCP requests and
responses in general. Perhaps NAME-Q and NAME-A (question and answer)?

Jesse
_______________________________________________
dcc2 mailing list
dcc2 at dcc2.org
http://six.pairlist.net/mailman/listinfo/dcc2
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.672 / Virus Database: 434 - Release Date: 28/04/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.672 / Virus Database: 434 - Release Date: 28/04/2004



More information about the dcc2 mailing list