Re: [hybi] WebSocket Version Numbers

Is there any real reason for using major and minor version numbers? Has any
protocol actually been able to use minor version numbers for anything useful
(e.g. both sides understand the major version but only one side understands
the minor version and it's still useful? 1.1 was a minor version upgrade to
HTTP and yet for all practical purposes it may as well have been 2.0.)

On Tue, Jun 21, 2011 at 4:40 PM, Greg Wilkins <gregw@intalio.com> wrote:

> On 21 June 2011 23:56, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> > On 6/21/11 7:10 AM, Bob Gezelter wrote:
> > Once again I recommend borrowing from the text in RFC 6120 if
> > appropriate, see Section 4.7.5...
>
>
> +1
>
> although I think we must now also say that a single integer should
> considered a minor version with major version being 0.
> So 8 == 0.8
>
> cheers
>
>
>
> > ###
> >
> >   The numbering scheme for XMPP versions is "<major>.<minor>".  The
> >   major and minor numbers MUST be treated as separate integers and each
> >   number MAY be incremented higher than a single digit.  Thus, "XMPP
> >   2.4" would be a lower version than "XMPP 2.13", which in turn would
> >   be lower than "XMPP 12.3".  Leading zeros (e.g., "XMPP 6.01") MUST be
> >   ignored by recipients and MUST NOT be sent.
> >
> >   The major version number will be incremented only if the stream and
> >   stanza formats or obligatory actions have changed so dramatically
> >   that an older version entity would not be able to interoperate with a
> >   newer version entity if it simply ignored the elements and attributes
> >   it did not understand and took the actions defined in the older
> >   specification.
> >
> >   The minor version number will be incremented only if significant new
> >   capabilities have been added to the core protocol (e.g., a newly
> >   defined value of the 'type' attribute for message, presence, or IQ
> >   stanzas).  The minor version number MUST be ignored by an entity with
> >   a smaller minor version number, but MAY be used for informational
> >   purposes by the entity with the larger minor version number (e.g.,
> >   the entity with the larger minor version number would simply note
> >   that its correspondent would not be able to understand that value of
> >   the 'type' attribute and therefore would not send it).
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>