Observe cancellation by client
See original GitHub issuenode-coap currently does not support proactive cancellation via GET with Observe=1.
In server.js
, the _handle()
function should probably try to find the corresponding ObserveStream via the token when request.headers['Observe'] === 1
instead of producing a new response with response = new Message(packet, function(response, packet)
. The ObserveStream needs to be closed. Sending the last (cached) response/notification with that token should work; otherwise, ObserveStream could also take a callback to produce a final response.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Observe cancellation by client #195 - coapjs/node-coap - GitHub
A client that is no longer interested in receiving notifications for a resource can simply "forget" the observation.` and the active ...
Read more >How To Handle Client Cancellations When Trying To Grow ...
The first thing you need to do when a client cancels is to find where those gaps are.
Read more >org.eclipse.californium.core.observe.ObserveRelation.cancel ...
Cancel this observe relation. This methods invokes the cancel methods of the resource and the endpoint. Popular methods of ObserveRelation. <init>. Constructs a ......
Read more >How to Stop Clients from Canceling Appointments Last Minute
Convincing clients to keep their appointments (or let you know in advance if they can't make it)? These tips reduce no-shows and prevent...
Read more >Cancellation, Part 1: Overview - Stephen Cleary
A CancellationToken can be any kind of cancellation: a user pressing a Cancel button; a client disconnecting from a server; an application ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You are right, I’ll close this issue. Thanks once again!
I think with the merge of PR #214 this issue is now fixed.