Client Sending PROTOCTL

[Winbots]

If I were to make a client (or script mirc), could a client send "PROTOCTL TOKEN ZIP"?

[medice]

why should a client send protoctl?

[aquanight]

TOKEN and ZIP are server-only. The only PROTOCTL option available to clients is HCN, which is the Hybrid Connect Notice which simply changes the connection notice (+s +c, though might apply to +s +F as well) from *** Client connecting on port 6667: nick (user@host) [classname] to *** Client connecting: nick (user@host) [ip.address] {classname}. Also the IP address is added to the end of Client exiting notices. Why it's needed? BOPM needs that format, so BOPM scanners connect with PROTOCTL HCN so that they don't have to resolve a hostname to scan for proxies . There may be other bots that rely on the hybrid connect notice as well...

[Winbots]

I was just thinking that it would be less b/w for both the client and the server if the client could use tokens, or zip, or both . Why make them server-only?

[Stealth]

I think a good reason to make them server-only, is because clients don't support that!

[codemastr]

If I were to make a client (or script mirc), could a client send "PROTOCTL TOKEN ZIP"?

Sure it could send it, but it wouldn't do anything. And there is good reason to make it server-only. First off, have you ever looked at TOKEN protocols? Every single IRCd uses its own set of tokens, there is absolutely NO standardization. So this means clients would need to maintain dozens of sets of tokens. Not to mention the fact that determining which IRCd software a server is running is difficult if not impossible. Then zip, as you might notice, there is no response from the server. The server does not say "Ok, I've accepted ZIP." So how does the client know whether the server accepted it or not? It doesn't. So there is no way for the client to ever know if the server supports zipping. Therefore, the client can never know when to zip and when not to.