Page 2 of 2

Re: ADC and the new clothes

Posted: 12 Aug 2009, 17:14
by Pretorian
Great suggestions. My only concern is how to deal with existing implementations?

Re: ADC and the new clothes

Posted: 12 Aug 2009, 20:13
by Pretorian
Having thought some regarding the SUP; instead there should be a protocol version for every feature. That is;
SUP ('AD' | 'RM') feature / protocol (separator ('AD' | 'RM') feature / protocol)*
where protocol is (say) major.minor
That way we can completely control and know which version of all features everyone is using. To keep some backwards compatibilty, all features that are "1.0" can omit the protocol version.

Re: ADC and the new clothes

Posted: 12 Aug 2009, 20:55
by Dj_Offset
Pretorian wrote:
Great suggestions. My only concern is how to deal with existing implementations?
My point exactly too, which is why i proposed it years ago when we broke the protocol after all...

Re: ADC and the new clothes

Posted: 13 Aug 2009, 07:07
by Pietry
Pretorian: The official ADC specification means BASE + official extensions ( at least that's what I ment ). And what do you think about the versioning of the protocol ? ( 1.0.1 versus 1.1 )