<div dir="ltr">From: <a href="https://swift.org/server-apis/">https://swift.org/server-apis/</a><div><br></div><div>"Base Networking" under "Focus Areas". </div><div><br></div><div>This was the first and last meeting: <a href="https://github.com/swift-server/work-group/blob/master/meetings/networking/2016-11-04/minutes.md">https://github.com/swift-server/work-group/blob/master/meetings/networking/2016-11-04/minutes.md</a></div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Nov 19, 2017 at 3:02 PM Helge Heß via swift-server-dev <<a href="mailto:swift-server-dev@swift.org">swift-server-dev@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
makes sense to me. What is that 'Transport group’? Is that a public thing?<br>
<br>
Sounds like it makes no sense to put more work into it right now. My PR should be fine to evaluate async behaviour of stuff the way it is.<br>
<br>
hh<br>
<br>
> On 19. Nov 2017, at 19:14, Tanner Nelson <<a href="mailto:tanner@qutheory.io" target="_blank">tanner@qutheory.io</a>> wrote:<br>
><br>
> This depends on what is happening with the Transport group AFAIK. If they are still planning to release some Swift I/O implementation we should probably wait for that to implement a real HTTP server.<br>
><br>
> However, I have no idea what the time frame is there. So it could make sense to get an improved server in the HTTP lib for the time being.<br>
><br>
> Tanner<br>
><br>
> Sent from my iPhone<br>
><br>
>> On Nov 19, 2017, at 11:23 AM, Helge Heß via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" target="_blank">swift-server-dev@swift.org</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> so what is the general feeling wrt<br>
>><br>
>> <a href="https://github.com/swift-server/http/pull/96" rel="noreferrer" target="_blank">https://github.com/swift-server/http/pull/96</a><br>
>><br>
>> do you want/plan to take this?<br>
>><br>
>><br>
>> I’m just asking to know whether I should waste more time on it. I think the bigger change I should probably do is to not use a dispatch channel but a dispatch source (this implementation has to do buffering anyways for pipelining, so channels do not gain us much). This would avoid some copying in specific best cases and might run a little better in performance tests.<br>
>><br>
>> hh<br>
>><br>
>> _______________________________________________<br>
>> swift-server-dev mailing list<br>
>> <a href="mailto:swift-server-dev@swift.org" target="_blank">swift-server-dev@swift.org</a><br>
>> <a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-server-dev</a><br>
<br>
_______________________________________________<br>
swift-server-dev mailing list<br>
<a href="mailto:swift-server-dev@swift.org" target="_blank">swift-server-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-server-dev</a><br>
</blockquote></div>