[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Extensions to the protocol.

To: Kurt Roeckx <Q@xxxxxxx>
Subject: Re: Extensions to the protocol.
From: Rico -mc- Gloeckner <mc@xxxxxxxxxxx>
Date: Thu, 16 Nov 2000 09:13:48 +0100
Cc: ircd-users@xxxxxxx
Delivered-to: ircd-users-out@irc.org
Delivered-to: ircd-users@irc.org
In-reply-to: <20001115233639.A3101@ping.be>; from Q@ping.be on Wed, Nov 15, 2000 at 11:36:39PM +0100
References: <20001115233639.A3101@ping.be>
User-agent: Mutt/1.2.5i

Heya,

Extensions which are common CAN be sent automagically to the Client.
Extensions which are specific, SHOULD be sent to the Client after the
Client asked for it. However the client MUST NOT wait for the Reply,
it MUST handle it like every other IRC Message: ask for it, but never
expect a Reply back (Replies MUST always handled asynchronous on IRC).

that all IMHO naturelement.


Hm. I wonder if there should be a global ircd-dev Mailingliste, which
offers a Forum between all ircd- and all Client-Coders.
Umm, maybe iam just dreaming.

-- Rico -mc- Gloeckner (mc@xxxxxxxxx) [RG2628-RIPE] 
mc @ irc.tu-ilmenau.de <http://www.ukeer.de> <sms@xxxxxxxx>
" > Linux is not user-friendly. " 
" It IS user-friendly. It is NOT ignorant-friendly and idiot-friendly."

Follow-Ups:
- Re: Extensions to the protocol.
  - From: Christophe Kalt

References:
- Extensions to the protocol.
  - From: Kurt Roeckx

Prev by Date: Extensions to the protocol.
Next by Date: Re: Extensions to the protocol.
Previous by thread: Extensions to the protocol.
Next by thread: Re: Extensions to the protocol.
Index(es):
- Date
- Thread