What would you change if you could?
Posted: 05 Feb 2011, 17:49
What would you change with ADC if you could, assuming you didn't need to care about current implementations och what is or isn't in the current spec?
Would you add a new feature? Remove one? Move an extension to the base spec?
What I'd (potentially) change (in no particular order);
•Add feature versioning
•separate app name from version
•add 'TS' in MSG to BASE
•add hash set (for directories etc)
•add SEGA to BASE (withholding the FCC of course)
•specify that 'adc' is an acronym for 'advanced direct connect'
•possibly separate chat functionality from file sharing in BASE
•'hidden' in the CT field in BASE
•possibly adding NAT-T to BASE
•add referrer in BASE for C-C
•allow other fields in SUP
•mandate that fields that signal FCCs shall use one convention for separator and that multiple FCCs are valid
•possibly clarify padding, endian etc for Base32, network order etc
•possibly clarify the message syntax for some types of parsers
•add invalid feature to STA
•allow for more error codes (break up severity and error code)
•add failover hubaddresses to BASE
•add free slots to BASE
•add locale field to BASE
•require that all clients send I4/I6
•possibly specify a common convention for hash field names
•possibly add an additional CT enumeration value for chat group
Would you add a new feature? Remove one? Move an extension to the base spec?
What I'd (potentially) change (in no particular order);
•Add feature versioning
•separate app name from version
•add 'TS' in MSG to BASE
•add hash set (for directories etc)
•add SEGA to BASE (withholding the FCC of course)
•specify that 'adc' is an acronym for 'advanced direct connect'
•possibly separate chat functionality from file sharing in BASE
•'hidden' in the CT field in BASE
•possibly adding NAT-T to BASE
•add referrer in BASE for C-C
•allow other fields in SUP
•mandate that fields that signal FCCs shall use one convention for separator and that multiple FCCs are valid
•possibly clarify padding, endian etc for Base32, network order etc
•possibly clarify the message syntax for some types of parsers
•add invalid feature to STA
•allow for more error codes (break up severity and error code)
•add failover hubaddresses to BASE
•add free slots to BASE
•add locale field to BASE
•require that all clients send I4/I6
•possibly specify a common convention for hash field names
•possibly add an additional CT enumeration value for chat group