Re: [core] Status of Blockwise Transfers

> On your first point, concurrent Block1/Block2 usage, that seems only applicable to POST or doesn't it?

From the spec, only concurrent POST is mentioned. In the Size extension draft, I proposed to get the resource size by the Size option, and use concurrent GET for blocks.
http://www.ietf.org/id/draft-li-core-coap-size-option-02.txt

And also I proposed to merge the Size draft and Block draft to allow this, and also other features.

Kind Regards
Kepeng
________________________________________
发件人: core-bounces@ietf.org [core-bounces@ietf.org] 代表 Dijk, Esko [esko.dijk@philips.com]
发送时间: 2011年10月31日 19:07
到: Kovatsch Matthias; core@ietf.org
主题: Re: [core] Status of Blockwise Transfers

Dear Matthias,

I agree with your second point that a server can't in general select a status code to a blockwise POST. It could be either 2.01, 2.02 or 2.04, or one of the error codes, but this depends on the entire payload being POSTed which is only known after the last block (Block1). Perhaps the server could send a "most likely to happen" response code. This is okay since only the final response status code (where M bit 0 in the Block1 option) actually carries the result of the REST operation  - see string "final response" in the text.

The current spec seems to already take this "most likely to happen" meaning for the status code in the examples, e.g. blockwise PUT returns 2.04 each time but if a block is missing the final result could still be 2.04 or 4.00 or 4.08. POST could do the same?

On your first point, concurrent Block1/Block2 usage, that seems only applicable to POST or doesn't it? It seems logical to me that the server can only start sending a blockwise response back (using Block2) when the full payload to POST has been received from the client (who uses Block1 and simultaneously empty Block2 to indicate size) and processed. For this text and/or examples are needed in my view.

regards,
Esko

-----Original Message-----
From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Kovatsch Matthias
Sent: Tuesday 25 October 2011 13:00
To: Carsten Bormann; core@ietf.org
Subject: [core] Status of Blockwise Transfers

Dear Carsten

I would like to ask about the current status of blockwise transfers:

- Concurrent usage of Block1 and Block2 in a single operation
  core-block-04 mentions it once, but does not specify how to handle it or give an example (I guess, a POST request keeps the Block1 option with M=0 and no payload until all Block2 blocks were requested?).

- Using Status codes before an atomic Block1 transfer is complete
  A POST could result in different actions, thus the server cannot provide it before the last Block1 request. Shouldn't the status be empty  when M=0 in a Block1 response?

Thanks a lot
Matthias
_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

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