Inject/queue a notification for the Server to dispatch about coap-rs

[justinh-xacom]

Sorry, we may be able to disregard/close my feature request, as the CoAP client that I'm looking to interface with may be able to handle notifications that come from somewhere different to where the initial GET+OBS request was sent. e.g.

• The CoAP client sends the GET+OBS request to the server IP targeting UDP port 5683.
• The CoAP server (Program A) acknowledges the request.
• The CoAP server stores the observer's IP, Port and Token within an observer list.
• Then, a separate program (Program B, which may or may not run on a different server), decides that a notification needs to be sent to an observer.
• Program B uses the observer IP, Port and Token from the observer list to send a notification packet that targets the observer's IP and Port.
• However, the notification comes from a source IP:Port that is not the same as the Server IP and Port that the client's GET+OBS request initially targeted.
• The CoAP client accepts the notification, and if the notification is confirmable, sends the acknowledgement to the notification sender (Program B) and not to the Server IP on UDP port 5683 (Program A).

Please give me a few days to confirm if I need the feature that my first post asked for. And if I no longer need this feature, and if nobody else adds a comment to say that they want this feature, I'll close it and apologise for wasting everybody's time.

[justinh-xacom]

I've confirmed that my distributed server approach does not work. i.e. A separate program that handles notifications separately to the main CoAP server is not feasible for the CoAP clients that my program needs to communicate with. The primary reason is that when we implement DTLS, I've been told that it will not be feasible to modify the CoAP client to accept notifications that come from a different IP:Port source.

So, to reword my feature request in simple terms...

Can a feature be added that allows the CoAP server, while running (i.e. while server.run() is listening for CoAP packets), to be told to send a notification packet to a specific CoAP observer?

[Covertness]

I don't think it's appropriate to implement in a CoAP library. The library should only contain implementations of the protocol. You can implement it by your self.

[Covertness]

Closed. Reopen it if you have any new problem about it.