* Timo Sirainen <[EMAIL PROTECTED]> [2001-10-19 14:42+0300]
> > While I don't think that all of those need to be implemented (and the
> > specification doesn't even say which ones are mandatory and which ones
> > are optional), I think that CLIENTINFO is a pretty important one since
> > it advertizes the client's capabilities.
>
> Did CLIENTINFO just return a list of all known CTCP commands? eg. "PING
> CLIENTINFO VERSION"?
Yes.
Here is what EPIC returns, for example:
12:18 CTCP CLIENTINFO reply from xy: SED UTC ACTION DCC VERSION CLIENTINFO
USERINFO ERRMSG FINGER TIME PING ECHO :Use CLIENTINFO <COMMAND> to
get more specific information
> Hmm.. but should it reply only those commands, or also
> commands that scripts and modules might have added? Maybe we'd need some
> ctcp_register() function which would tell CLIENTINFO which ctcp replies are
> known.
Yes, the ctcp_register() function sounds like a nice way to go.
Thanks,
Hugo
--
Hugo Haas <[EMAIL PROTECTED]> - http://larve.net/people/hugo/
I love it when a plan comes together! -- John "Hannibal" Smith
