-
Notifications
You must be signed in to change notification settings - Fork 51
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
Support for rfc8323 (CoAP over TCP) #33
Comments
Good idea. But I think it need a long time. |
The trickiest part of TCP rfc is a different wire/serialization protocol.
Beyond tat, it’s relatively close to existing library.
…On Fri, Jan 25, 2019 at 4:00 AM Covertness ***@***.***> wrote:
Good idea. But I think it need a long time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APu4MsP6FluwWQkE09-w67tiObTLCYcPks5vGvHJgaJpZM4aRZEa>
.
|
I will consider to implement it in the future. Beside, any pr about it will be appreciated. |
I'm in! |
Hi! Has there been any progress on this front? |
Studies are going crazy now.. I believe it is feasible but that we could focus on more mature issues |
any progress? |
Still not implement. Do you have any interest in it ? |
Hello @Covertness, I apologise for being busy. I think it is better to see with someone else to do this contribution. |
It's fine |
This is more of a question, rather than an issue, but curious if there are any plans to support TCP RFC (https://datatracker.ietf.org/doc/rfc8323/) for coap-rs.
The text was updated successfully, but these errors were encountered: