Lars, Thanks for the feedback. The Representation class indeed carries both metadata (equivalent to HTTP headers) and content bytes.
You are correct about the "allowedMethods" property, it should be associated to Representation instead of Response. Actually, according the HTTP 1.1, it could be even part of a PUT request: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.7 I will change this later today. Another limitation that I can see in the current implementation (not the API itself) is that the Response instances for HEAD methods received by the HTTP client don't set an "empty" instance of Representation with the metadata set. I will also fix that. Best regards, Jerome > -----Message d'origine----- > De : Lars Heuer [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 18 octobre 2006 13:57 > À : Lars Heuer > Objet : Re: b19 - Entity > > [...] > > But acc. to HTTP/1.1 contains an Entity the *header* and an > optional > > *body*. But in Restlet this is not the case: "getEntity" > returns the > > *body* of the Entity. > > Well, not really, the Representation carries values that belong to > the header, but not all. I think another (neutral) term avoids > confusion. I.e. the "Allow" header is one of the "standard" Entity > headers acc. to HTTP/1.1, but it is not possible to set / get this > header from the value returned by "getEntity". Beside that other > headers are allowed as Entity headers, but this is also not supported > by the Representation. > > Best regards, > Lars > -- > http://www.semagia.com > >
