Multiple values for one key in requests/responses

Tomi Pieviläinen tpievila at cc.hut.fi
Thu Mar 1 16:03:36 UTC 2007


On Thu, Mar 01, 2007 at 10:53:02AM -0500, Rowan Kerr wrote:
> On 3/1/07, Tomi Pieviläinen <tpievila at cc.hut.fi> wrote:
> > I don't see how different keys could work but a
> > delimiter would be fine. There needs to be a reasonable way to
> > negotiate common capabilities between the RP and OP.
> 
> For assoc_type, I thought the idea was that the RP tries its preferred
> method, and the OP will say if it supports that assoc_type or not ..
> then the RP can re-try with a different assoc_type until it finds one
> that works.

The spec says that OP may respond with a supported assoc_type. Going
back and forth would seem really unnecessary, when it is very simply
possible to send a list of supported association types in preferred
order.

-- 
Tomi Pieviläinen, +358 400 487 504
"I will sit down now, but the time will come when you will hear me."
- Benjamin Disraeli, 1st Earl of Beaconsfield
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20070301/44b48720/attachment-0002.pgp>


More information about the specs mailing list