Re: [core] Suggestions re: how to implement HEAD semantics within COAP?

I guess the Size option from draft-li-core-coap-size-option-00 could be extended such that a CoAP GET request including Size=0 is treated as a request to get the size of the resource representation (but not the resource payload) and so could be translated to and from an HTTP HEAD (and could return Content-Length to a CoAP requester).

-----Original Message-----
From: core-bounces@ietf.org on behalf of Paul Duffy
Sent: Sat 07/05/2011 05:27
To: Carsten Bormann
Cc: core
Subject: Re: [core] Suggestions re: how to implement HEAD semantics within COAP?

On 5/6/2011 12:20 PM, Carsten Bormann wrote:
> On May 6, 2011, at 17:54, Paul Duffy wrote:
>
>> The use case is HTTP HEAD into a COAP network to determine the size of a resource.
> HTTP HEAD gives you a content-length only if HTTP GET would have given you a content-length.
> So this usage of HTTP HEAD is a bit on thin ice on the HTTP side already.
>
> Can you explain the use case for "HTTP HEAD into a COAP network to determine the size of a resource"?

The example is probably better expressed in the opposite direction.

A COAP based element needing to determine the size of a large resource 
before loading it from an HTTP network.

> Why would you ever want to do that?
> And does this use case occur often enough to warrant any optimization?
>
> Gruesse, Carsten
>
>

_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

--------------------------------
Onzo is a limited company number 06097997 registered in England & Wales. The    
registered office is 6 Great Newport Street, London, WC2H 7JB, United Kingdom.

This email message may contain confidential and/or privileged information, and
is intended solely for the addressee(s). If you have received this email in     
error, please notify Onzo immediately. Unauthorised copying, disclosure or 
distribution of the material in this email is forbidden.
--------------------------------