[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Question: It's possible to implement connector with non-ip protocol? #1722

Closed
Michal-Wadowski opened this issue Sep 9, 2021 · 4 comments
Closed

Question: It's possible to implement connector with non-ip protocol? #1722

Michal-Wadowski opened this issue Sep 9, 2021 · 4 comments

Comments

@Michal-Wadowski
Copy link
Michal-Wadowski commented Sep 9, 2021 •
edited
Loading

Hi everyone!

While I'm trying to implement some functionality of eclipse-leshan/leshan#1046 I try to implement some custom connector (experimental, proof of concept for now) which would be non-ip protocol.

This connector is returning protocol "N" as non-ip. But while initializing CoapEndpoint there is call CoAP.getSchemeForProtocol() with "N" as parameter and it throws an error: "Protocol N not supported!".

If I avoid this (by placing placeholder for example "UDP") then I get another issue: connector has to implement getAddress() which has to return non-null address. But for non-ip protocols there is no InetSocketAddress address.

Is it possible to avoid these issues, or I'm not understand enough subject and I'm doing this in a wrong way.

Best Regards
@sbernard31
Copy link
Contributor

@madhushreegc do you face this kind of problem too ?

@boaks
Copy link
Contributor
boaks commented Sep 9, 2021 •
edited
Loading

For the current flavors, there are some dependencies on the message format (e.g. UDP RFC7252, TCP RFC8323), and there are defined schemes, e.g. "coaps+tcp".
For me the point to start with would be:

  • does it use one of both currently implemented formats? Then I would just start with re/miss-use one of the current names.
  • does it introduce a new message format? Then that would require more work and adaptions.

As example: I implemented a Connector, which uses AT-cmd. Though this an other UDP/DTLS implementation, I used that name.

@boaks
Copy link
Contributor
boaks commented Sep 9, 2021

See also leshan - issue 1046.

@boaks
Copy link
Contributor
boaks commented Sep 19, 2021

I think, this one is just done. (Or the interest is lost).
If you have any further questions, don't hesitate to add a new comment or create a new issue.

@boaks boaks closed this as completed Sep 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sbernard31 @boaks @Michal-Wadowski