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

[Thijs Metsch]

forget it...I just misinterpretted your statement...*sorry*

-----Original Message-----
From:	occi-wg-bounces at ogf.org on behalf of Thijs Metsch
Sent:	Wed 11-Aug-10 14:13
To:	Edmonds, AndrewX
Cc:	occi-wg at ogf.org
Subject:	Re: [occi-wg] HTTP Header Serialization Format, use of Attribute header

On Wed, 2010-08-11 at 11:52 +0100, Edmonds, AndrewX wrote:
> Attribute: occi.compute.speed=2.4
> ...
> 
> My experience is that many web frameworks do not observe 2616
> correctly. Taking tomcat and associated frameworks; if I send such a
> request as above the only header that I will receive is the last one,
> not all. Web.py also exhibits this same behavior. As a result you will
> always have to formulate your request as such:

web.py doesn't do this for the following example...Only Categories and
Links would ned to be listed....

-Thijs

> Attribute: occi.compute.cores=2, occi.compute.speed=2.4
> 
> This particular issue is not a problem using a request like:
> 
> ...
> occi.compute.cores=2
> occi.compute.speed=2.4
> ...
> 
> However the issue remains for Link and Category headers.
> 
> Andy 
-- 
Thijs Metsch
Senior Software Engineer Grid and Cloud Technology
Platform Computing GmbH
Europaring 60
D-40878 Ratingen
http://www.platform.com

http://www.nohuddleoffense.de/ - http://www.twitter.com/befreax

_______________________________________________
occi-wg mailing list
occi-wg at ogf.org
http://www.ogf.org/mailman/listinfo/occi-wg



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/occi-wg/attachments/20100811/ec3b1525/attachment.html