I assume you refer to the openid parameter. This parameter is not general purpose but problem specific. Thus it is in my opinion not suited as an example for a general purpose standard.
regards, Torsten. Marius Scurtescu <mscurte...@google.com> schrieb: On Fri, Jun 17, 2011 at 12:13 PM, David Recordon <record...@gmail.com> wrote: > +1 Eran > > On Fri, Jun 17, 2011 at 12:46 AM, Eran Hammer-Lahav <e...@hueniverse.com> > wrote: >> OAuth has been successful because of its simple architecture and because it >> is based on actual deployment experience. Offering multi-token responses >> would be premature standardization. I am not convinced that adding it later >> would entail any real technical difficulty. +1 OpenID Connect is a good example that adding it later is not that difficult. In this case the other token is returned as a separate parameter, which is much better IMO than an array. Marius _____________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth