<font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">Chris</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Alex Blewitt via swift-server-dev
<swift-server-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Andrew Akira Toulouse
<andrew@atoulou.se></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">swift-server-dev <swift-server-dev@swift.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">30/10/2016 08:40</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [swift-server-dev]
Netty would be a good framework to look at</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">swift-server-dev-bounces@swift.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2><br>
> On 30 Oct 2016, at 01:01, Andrew Akira Toulouse via swift-server-dev
<swift-server-dev@swift.org> wrote:<br>
> <br>
> 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).<br>
<br>
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.
<br>
<br>
Alex<br>
_______________________________________________<br>
swift-server-dev mailing list<br>
swift-server-dev@swift.org<br>
</font></tt><a href="https://lists.swift.org/mailman/listinfo/swift-server-dev"><tt><font size=2>https://lists.swift.org/mailman/listinfo/swift-server-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>