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

[Michal-Wadowski]

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]

@madhushreegc do you face this kind of problem too ?

[boaks]

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]

See also leshan - issue 1046.

[boaks]

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.