-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce a CoapMessage class/interface ? #83
Comments
Easy one would be to add helper method, would that be enough? |
I'm not sure to see how it will looks like ? |
Something like:
|
OK I get it but my question was more about having a kind of Parent class (e.g. Regarding adding this static method, to be honest, I'm not sure will really makes my user code better. 🤔 Anyway, maybe better to work first on #84 and see if you also need this kind of abstraction in java-coap code too ? |
I don't know if this is a good idea but I face some situation where I need to handle a coap request OR a coap (separated) response in a same way. This is not too surprising as from a CoAP RFC point of view all request and response are conceptually a CoAP Message.
In my case, I need the remote peer address and the transport context of the message.
See :
The text was updated successfully, but these errors were encountered: