Version Handling [ was OpenID status update ]

[Jason Nelson]

If a version is invalid (or not specified) we can assume it to be 1. Once we 
add new versions or features; we can use a version flag so clients and 
servers can negotiate a protocol. I don't see any importance in addressing 
it now.
  On 6/6/05, Martin Atkins <mart at degeneration.co.uk> wrote: 
> 
> Paul Crowley wrote:
> > In the end, if we want to introduce totally incompatible protocol
> > changes, we can always tack a version number on to the openid.mode
> > parameter. Any client or server that gets a request or response with an
> > unrecognised openid.mode is going to reject it appropriately.
> 
> As soon as there is a totally incompatible protocol change, we might as
> well throw in the towel. If a new version breaks old servers/consumers,
> then it might as well not be OpenID anymore.
> 
> It's far more likely that future changes will be implied by new
> parameters. I see no value in allowing for a case which breaks
> everything anyway.
> 
> 
> 
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.danga.com/pipermail/yadis/attachments/20050606/d4f16c14/attachment.htm