Skip to content
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

added TCP support for server and client APIs #3

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

sking2600
Copy link

While messageTCP.go handled all of the packet formatting, the client and server API's were tightly coupled to the UDP transport. This commit abstracts the transport with the pre-existing coap.Conn struct and more media types were added including CBOR, OCF and LWM2M

ccollins476ad and others added 11 commits March 13, 2017 15:56
This commit incorporates the modified CoAP header for TCP, as defined in
https://tools.ietf.org/html/draft-ietf-core-coap-tcp-tls-06.
Short messages would have the incorrect length encoded!
Prior to this change, Message and TcpMessage could not be used
interchangeably.  Now, Message has been converted to an interface,
TcpMessage implements the interface, and the struct previously known as
Message is now called DgramMessage.
Add API to set URIQuery to a message
Add API to set Observe option to a message
@sking2600
Copy link
Author

Additional work to be done once/if this PR is merged would be to better align the client and server API's with the net/http package from the stdlib. Ideally, it'd be possible to have go-coap be a drop in replacement for net/http in popular router packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants