[swift-server-dev] Netty would be a good framework to look at

[Chris Bailey]

As Alex says, we actually have some of the contributors/committers for 
Netty signed up to the work group - Tom Doron is one of them.

That means being able to build a highly performing async framework is very 
much in our minds. We are also trying to build functional APIs though, 
meaning we also have to make sure we support wider use cases - including 
providing the ability to create a framework that does thread based 
blocking I/O if you want to.

Chris




From:   Alex Blewitt via swift-server-dev <swift-server-dev at swift.org>
To:     Andrew Akira Toulouse <andrew at atoulou.se>
Cc:     swift-server-dev <swift-server-dev at swift.org>
Date:   30/10/2016 08:40
Subject:        Re: [swift-server-dev] Netty would be a good framework to 
look at
Sent by:        swift-server-dev-bounces at swift.org




> On 30 Oct 2016, at 01:01, Andrew Akira Toulouse via swift-server-dev 
<swift-server-dev at swift.org> wrote:
> 
> I've used a couple of networking/server/web frameworks over the years, 
and the one that stands out for me is Netty. Netty is a highly 
asynchronous Java framework used in very high-performance applications 
(including hedge funds and Wall Street, for example).

Yes, Netty is an excellent framework and there have been some discussions 
already with some of the Netty team. One open question is how to map the 
asynchronous behaviour into supported constructs in Swift, such as 
libdispatch, which means it isn't just a drop in API but needs further 
investigation. 

Alex
_______________________________________________
swift-server-dev mailing list
swift-server-dev at swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-server-dev/attachments/20161030/ba51749a/attachment.html>