You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Could you please clarify how is this different than Leshan?
Does it provide better performance?
I see it lacks few features like Lack of DTLS support but what are its main points where it stands taller than Leshan.
Thanks, Santos
The text was updated successfully, but these errors were encountered:
Well when I started the project I was a bit over ambitious of the scope. I was also learning the spec and what better way than to implement it.
since then I found that there was absolutely no reason for another implementation of the server. There has been a lot of quality effort poured into that by some talented folks.
A client would still make sense and would be better use of my time,IMO.
I've created another issue #44 to highlight the fact that I will be refactoring the project heavily to make it client only and remove the server implementation.
The Go language itself has lots of nice things going for it.
With regards to DTLS, it would be soon coming. I've implemented recently dTLS support in the dependent CoAP library also written by me(Canopus). I'm taking my time a bit so that I'm satisfied with the implementation. After that the refactoring of betwixt will incorporate that.
any update on this
I have all my application running in go and I would like to add the LWM2M with DTLS support
that would be a great add on
really appreciate your work
Hi,
Could you please clarify how is this different than Leshan?
Does it provide better performance?
I see it lacks few features like Lack of DTLS support but what are its main points where it stands taller than Leshan.
Thanks, Santos
The text was updated successfully, but these errors were encountered: