[occi-wg] HTTP Header Serialization Format, use of Attribute header

[Ralf Nyren]

If there are no objections I say we reintroduce the Attribute header.

I can update the wiki page (HTTPHeaderRendering) accordingly. I then  
suggest we use it as a basis for discussion at the conference call next  
Wednesday and if you decide to decline the change we can just revert back  
to the old version.

regards, Ralf

On Wed, 11 Aug 2010 13:21:00 +0200, Edmonds, AndrewX  
<andrewx.edmonds at intel.com> wrote:

> Good points and no objections from me :-)
>
> -----Original Message-----
> From: Ralf Nyren [mailto:ralf at nyren.net]
> Sent: Wednesday, August 11, 2010 12:14 PM
> To: Edmonds, AndrewX; occi-wg at ogf.org
> Subject: Re: [occi-wg] HTTP Header Serialization Format, use of  
> Attribute header
>
> Yes, I am aware of the problems and thus currently only use the
> comma-separated list format for outgoing data.
>
> But as you said we still have this problem for Category and Link headers
> in any case so I do not see why the specification would try to  
> accommodate
> the web framework, etc problems for just attributes. I mean, the whole
> bootstrap/discovery process depends on the ability to send multiple
> Category headers.
>
> A more solid argument as I see it is one of robustness. With the  
> Attribute
> header we tag all the supplied values as being attributes and nothing
> else. For a client this means it can display unrecognized (vendor)
> attributes to the user and a server can respond with an appropriate error
> message for any attributes it does not support. Without the Attribute
> header unrecognized attributes would just be silently discarded.
>
> regards, Ralf
>
>
> -------------------------------------------------------------
> Intel Ireland Limited (Branch)
> Collinstown Industrial Park, Leixlip, County Kildare, Ireland
> Registered Number: E902934
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.