Multiple values for one key in requests/responses

[Dick Hardt]

Conscience design decision to not allow multiple values per key as  
some languages (PHP) it is hard to differentiate them.

Solution is either have different keys for each value, or define  
delimiter so that you can have multiple values contained in the one  
value string for a given key.

-- Dick

On 25-Feb-07, at 11:51 PM, Tomi Pieviläinen wrote:

> Hi,
>
> After reading the new draft specifications, I can't find a way to send
> multiple values with same key on a message.
>
> I started to think about this when I thought that it should be
> possible for the RP to tell the OP that multiple assoc_types are ok
> (and vice versa, if more hash functions are included in the future).
> Now even if the RP does support multiple algorithms, you can only
> choose one.
>
> Am I missing something, or is this a design choice? If so, could you
> point me to the reasoning (I've followed only the 2007 discussions
> regarding the new spec)?
>
> -- 
> 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
> _______________________________________________
> specs mailing list
> specs at openid.net
> http://openid.net/mailman/listinfo/specs