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

[Edmonds, AndrewX]

What's in the doc book version is not the current version.
Speaking from an implementer's point of view (mine) removal of "Attribute:" has made parsing of header key/values easier. Personally, I have no strong tie to either approach.

Andy

-----Original Message-----
From: occi-wg-bounces at ogf.org [mailto:occi-wg-bounces at ogf.org] On Behalf Of Ralf Nyren
Sent: Wednesday, August 11, 2010 11:27 AM
To: occi-wg at ogf.org
Subject: [occi-wg] HTTP Header Serialization Format, use of Attribute header

Hi,

Reading the updated spec on Http Header Rendering [1] I see you have  
changed the way attributes are represented in the HTTP header. In the  
latest docbook spec OCCI resource attributes are specified using the  
"Attribute" header, e.g.:

GET /compute/xxx HTTP/1.0

HTTP/1.0 200 OK
Attribute: occi.compute.speed=2.0
Attribute: occi.compute.memory=1.0

In the latest spec however it would look like this instead:

HTTP/1.0 200 OK
occi.compute.speed: 2.0
occi.compute.memory: 1.0

What is the motivation behind this change?

I believe the Attribute header is a much more clean approach since it does  
not pollute the HTTP header namespace with (perhaps) arbitrary names (you  
have to consider vendor extensions as well).

regards, Ralf

[1]  
http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/HTTPHeaderRendering?wikiPageVersion=9
_______________________________________________
occi-wg mailing list
occi-wg at ogf.org
http://www.ogf.org/mailman/listinfo/occi-wg
-------------------------------------------------------------
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.