Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cf-dev] Replacing the element-connector with Netty -- thoughts?

Hi,
Netty is quite big compared to element-connector. it's comming with it's own threading model, and without rewriting the threading part of Californium it doesn't make sense for the UDP server. (I'm quite sure NIO frameworks make sense at all for UDP servers)

Having a dependency to netty for the TCP implementation is ok, for calfornium/scandium, UDP, I don't think it's a good idea for just implementing the Channel interface.

If the goal is to make Scandium consumable by netty user, let's just create a scandium-netty project implementing the netty Channel interface?

Julien

On Tue, Mar 17, 2015 at 7:45 PM Kovatsch Matthias <kovatsch@xxxxxxxxxxx> wrote:
Hi all

I have been thinking about getting rid of the element-connector since I created it. It was introduced to decouple Scandium from Californium, so that it can be used as stand-alone DTLS implementation. Netty [1] is a powerful framework that provides something similar (actually much more). While getting rid of the custom element-connector, it might also lead to a performance gain.

Since Simon Lemay is now working on the TCP/TLS binding, it appears to be a good time to start with the replacement. Simon checked that Netty is also supported by Android and runs on the Raspberry Pi.

Any comments? Does anyone have experience with Netty, maybe situations where it actually did not fit?

For the long-term, it might also help for DTLS. Netty does not have DTLS yet, but I would say they need it. Scandium is by no means a high-performance implementation and still requires lots of work, in particular for testing and security analysis. But maybe we can get more contributors or an alternative that is better for both communities!

Ciao
Matthias

[1] http://netty.io/
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev

Back to the top