Command Types (Experimental)

The fallowing commands are experimental and many have not been implemented yet. I feel that these commands are required to combat the level of fake sharing on the network.
The following section describes the format of the Commands, Each field is denoted with < >.
The fields in the command are separated by a single space character (ASCII 32).
And each Command ends with a | (pipe). All Commands are case sensitive.

$MyINFO

This is a modified version of the $MyINFO command that I feel will be useful.

$MyINFO $ALL <nick> <interest>$ $<speed>$<e-mail>$<sharesize>$<slots>$<onlinetime>$

• <nick> is the client's nick.
• <interest> is a string describing the user's interest and may be empty (All characters except $ and | are allowed).
• <speed> is a string describing the client's internet connection selected from "56Kbps", "Satellite", "DSL", "Cable", "LAN(T1)", and "LAN(T3)" followed by a byte indicating the speed class. The value of the byte is selected from at least 1 for 56Kbps, 3 for cable or DSL, or 7, also for DSL.
• <e-mail> is nick's e-mail address and may be "".
• <sharesize> is the number of bytes this client shares as a string.
• <slots> is the nuber of free slots / the total slots.
• <onlinetime> is the time the client application is online. The format should be Days:Hours:Minutes.

$Supports BZList

This command is currently supported by DC++ to notify the downloading client that a BZList is available if their are no free slots.

$Supports BZList

Currently this command is only sent in the Client to Client communication and is sent by the client that is being connected to immediately after the $Lock command.

To improve apon this design I belive that this command should be refined in its use. For instance, if this command is sent the client should send a BZList regardless of the free slots status. The old style DCLst should only be sent if the client does not support BZLists.