Comments (10)
Have you try the example? I think it can be work just change the client method get
to put
from coap-rs.
It might be because client and server are in different threads in the example? I might have to try that.
from coap-rs.
Gave it a try, using that same example and changing CoAPClient::get(url)
with CoAPClient::put(url, vec![])
gives the same error as before.
from coap-rs.
let response = CoAPClient::put(url, vec![]).unwrap();
works on my computer. Which OS you are using?
from coap-rs.
from coap-rs.
Maybe. The error occur on a non-blocking socket. The linux has its' own non-blocking system. Have you try to start the client a little later?
from coap-rs.
That was it, adding a barrier (a oneshot channel too, pretty much anything to sync them up) was enough for the example to work. I still think the underlying problem is not resolved, but maybe this could be added as a workaround? It would be useful to have this in an example, as part of the documentation or even inside the library itself (if it makes sense).
from coap-rs.
It relates to the OS type. Only a few of OS has the problem. I will add some comments in the example later.
from coap-rs.
Also, add that the thread is mandatory, otherwise it produces an error as well.
from coap-rs.
commented
from coap-rs.
Related Issues (20)
- Generic subject observer (RFC 7641) support HOT 5
- Server::run abruptly returns when a response payload is too large HOT 4
- Observe requests crash server if the client uses an empty vec![] to represent Observe: 0
- Migrate to Rust 2021 edition HOT 1
- Crash when using python aiocoap HOT 2
- Unexpected panic due to network connectivity state HOT 1
- Outdated documentation refrenced HOT 1
- Message IDs and tokens not set HOT 2
- Client: Separate responses not processed HOT 2
- GET, POST etc. with Uri-Host HOT 2
- Blockwise transfer for with a request payload HOT 4
- Server response retransmission due to duplicate client request (duplicate MID) HOT 3
- Update coap-lite dependency HOT 2
- 0.12.2's update of coap-lite is incompatible HOT 1
- No easy way to set options in client requests HOT 8
- The observer implementation and my use case HOT 7
- Mio 1.8.8 incompatible with newer Tokio versions HOT 3
- observe uses hard-coded default receive timeout HOT 1
- Inject/queue a notification for the Server to dispatch HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from coap-rs.