-
Hi,
In one scenario we noticed that on receiving unexpected ETag in blockwise transfer, observe token was removed but CoapHandler doesnt get notified about observe being deleted. We understand that…
-
First, apologies if the issue is not clear as I am pretty new to coap and californium .
I am using californium 2.0.0.SNAPSHOT release. our server side is a device that supports only 32 bytes block …
-
Branch 2.0.x
See comments in #527
Though a compliant server CAN answer with 2.03, if a californium client uses the ETAG in the request to select the resource version, californium breaks the tra…
boaks updated
6 years ago
-
Hi,
I wasn't sure if I should post this here or in the Leshan project, but since there are some common contributors, I'll post it here.
In our current Lwm2m project, we have no choice but to imple…
-
We're facing an issue were one of our clients (using Wakaama) is returning 2.31 response codes on Block transfer writes. As far as I can see this is a valid response for block transfers, but it is rej…
-
The blockwise layer does not verify if all inbound requests that are part of the same transfer also contain the same sender identity.
-
Hi,
The last line in your code does not save images as TIFFS, nor preserves metadata.
The consequence is that uploading these images to Pix4D or Agisoft is useless, since all the metadata is los…
-
Would be great to have a flag to split large files into smaller encrypted files. This would allow for people to take advantage of the unlimited cloud storage offerings which have max file size limits…
-
```
Hi, Kevin and Randy,
as discussed during your visit in Berlin I just open a new issue for all questions
and comments related to the further development of the optional pressure solver ScaRC.
A f…
-
Scenario:
1. Retransmission count set to 8. (MAX_RETRANSMIT=8).
2. Get observe is active (Token=9953ef769546f8bb) and data is being received in blockwise transfers.
3. At 11:49:38, for one blockwis…