ADC/0.12 Discussion ------------------- Read the full protocol draft at: http://dcplusplus.sourceforge.net/ADC.htm Here is my thoughts about the changes needed to the protocol; * The "BASE" protocol I suggest making the commands "SCH", "RES", "GET", "GFI" and "SND" (+ certain flags to INF and STA) so called "BASE" commands. It should be possible to use ADC as a message protocol without file sharing involved in the implementation. If this would allow us to use ADC as a a "SIP-light" protocol. I'll show some cool protocol extensions later, I promise :) Now, let's have a look at the commands: * SUP does not specify the protocol version to be used. I suggest we change the command signature from: SUP ('AD' | 'RM') feature (separator ('AD' | 'RM') feature)* to SUP protocol (separator ('AD' | 'RM') feature)* Where 'protocol' is the protocol string such as 'ADC/0.12' (the same as CTM). The differences between ADC/0.11 and ADC/0.12 (D vs E messages) should be an obvious argument for this. A hub could decide to translate between clients supporting these. Also the mandatory feature is removed. * The STA x46 (invalid IP supplied in INF) suggests using the flag 'IP' to specify the correct IP. The specification should read 'I4' and 'I6' for IPv6 protocol consistency. * INF - US and DS = bits/sec - AS = bytes/sec I suggest using bytes/sec for 'US' and 'DS' flags for consistency. This also gives a slightly shorter string as a bonus.