You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFC 8323 specifies CoAP over TCP instead of UDP. Roughly speaking, the protocol is the same as in the UDP case, but measures that let the application detect duplicate messages and resolve ordering issues are not included within the TCP version of CoAP.
Questions that come to my mind are:
Is there any intention/timeline to support CoAP over TCP (or even TLS)?
Does an integration of the TCP case make sense to include in the current library? Can one estimate the refactoring efforts?
Thanks!
The text was updated successfully, but these errors were encountered:
@gbrgr I think concrete plans or a timeline does not exist :-) So in fact check the code and we are happy to get a PR :-)
In fact when I read the code (veeeery rough checkup) correctly then it already could work if you initialize your tcp server outside and pass it as first parameter to the "listen" method - it needs to be an EventEmitter and emit events like the dgram socket. In fact mainly two places interact with dgram ... the server class and the agent class, so refactoring also to officially support tcp should be not too complex
RFC 8323 specifies CoAP over TCP instead of UDP. Roughly speaking, the protocol is the same as in the UDP case, but measures that let the application detect duplicate messages and resolve ordering issues are not included within the TCP version of CoAP.
Questions that come to my mind are:
Thanks!
The text was updated successfully, but these errors were encountered: