Jozef Kralik

@lx121451 Pls, why do you need `block2`? Thx

> Do you recall why the `Block2` option is removed from the message before its passed to the `next` handler function? Maybe the error check is inverted? No, it's correct.

For test you can use https://github.com/plgd-dev/go-coap/blob/master/options/commonOptions.go#L278 to watch all messages that comes to server in `v3`. I will close the issue, feel free to reopen it.

v3 contains the functions that allow you to modify message directly: https://github.com/plgd-dev/go-coap/blob/b8901963ae43acd9a14f98b3d47ec17b26b38e7a/net/responsewriter/responseWriter.go#L59 https://github.com/plgd-dev/go-coap/blob/b8901963ae43acd9a14f98b3d47ec17b26b38e7a/net/responsewriter/responseWriter.go#L65

@Sean-Der From my point view, spawning goroutine's below to underlayer of dtls/listener, because we want to have similar API as tls.Listener. and it is more convenient for using. Of course...

@rtechencheng The second commit with dropping connection is not needed because the connection will be closed by deferred function in session.Run(). From my point of view, it seems that the...

The `Done()` just notifies that session(socket) was really closed. We are using it to check that the file descriptor was really closed. You can set up your error function to...

Fixed in `v3`. Fill free to reopen it, if not.

@beriberikix @tim-golioth As we prepare to release version 3, I would like to ask if you have any changes from the API side that need to be made, or if...

@emmanuelay > 1. How do I access the message ID that the client sent to the server from within the handler above? > The reason is that I want to...