When BlockwiseLayer is manually turned off, NullPointerException is thrown. about californium HOT 3 CLOSED

Hi @wiinguyen,

I am not really sure about the intent of your issue report. Are you asking for help regarding how to disable blockwise support? I am asking because this is not a configurable option in Californium (yet).
May I also ask why you want to disable the blockwise layer in the first place?

from californium.

Hi Kai,

Please see inline.

On Jul 21, 2016, at 9:40 AM, Kai Hudalla [email protected] wrote:

Hi @wiinguyen,

I am not really sure about the intent of your issue report. Are you asking for help regarding how to disable blockwise support?

Yes, I'm integrating a reliable transport solution which has its own alternative blockwise protocol. Thus, blockwise is not needed in this case.

I'm not convinced that the blockwise would be needed either for CoAP+TCP <--> CoAP+TCP. This needs to be evaluated.

I am asking because this is not a configurable option in Californium (yet).
May I also ask why you want to disable the blockwise layer in the first place?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

from californium.

Well, even with using TCP as the transport, using blockwise has some advantages, e.g. when transferring larger payloads using blockwise you are not blocking the transport channel for the entire transfer time because the transfer is done in smaller chunks leaving room for other messages being multiplexed into the stream.
Support for disabling blockwise should best be done by introducing a configuration option, I guess. Much along the lines of the way the reliability layer can be configured to support congestion control.

from californium.