Felix Letkemann (personal)

The same issue exists when using sinatra. The parameters variable will be converted to this very strange format mentioned above. Current example: ```{ position: { lat: 3.14, lng: 49.2332, imei:...

Yes, I do use rack 2 and I would not like to downgrade to 1.6.8 since that breaks the compatibility with some other gems I use. Maybe you could give...

Maybe the error is happening outside of david. I have noticed, that the function dispatch already gets the data corrupted. It looks like the UDPSocket is delivering corrupted data. Also,...

Maybe the bug is caused by the recvmsg_nonblock method? Maybe that limits the number of chars that can be read at a time.

Your guess was correct, the maximum block size set by copper was the reason for all the trouble I have had. Unfortunately, I do not have the deep knowledge about...

I have noticed that there is still some strange escaping behaviour, even if there is no problem with block wise transfer. After spending quite some time I noticed, that the...

This ``` {"{ position: { lat: 3.14, lng: 49.2332, imei: 9FJ489FJW938FJW39F8"=>nil} ``` is probably not the serialized version of ``` { position: { lat: 3.14, lng: 49.2332, imei: 9FJ489FJW938FJW39F8JW39F }...

Since accessing the sinatra routes over CoAP, the workaround is the following: ``` post '/blub/hallo' do puts "\n\n\n\n" puts params.inspect puts "\n\n\n\n" 'Test Antwort' end get '/.well-known/core' do content_type 'application/link-format'...

Maybe I can add this feature as soon as I get a little deeper into coap and into the internal logic of the david gem. At the moment, I would...

I have got the same issue here!