[swift-server-dev] PR 96 - async server

[Helge Heß]

Hi,

makes sense to me. What is that 'Transport group’? Is that a public thing?

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.

hh

> On 19. Nov 2017, at 19:14, Tanner Nelson <tanner at qutheory.io> wrote:
> 
> 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. 
> 
> 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. 
> 
> Tanner 
> 
> Sent from my iPhone
> 
>> On Nov 19, 2017, at 11:23 AM, Helge Heß via swift-server-dev <swift-server-dev at swift.org> wrote:
>> 
>> Hi,
>> 
>> so what is the general feeling wrt
>> 
>> https://github.com/swift-server/http/pull/96
>> 
>> do you want/plan to take this?
>> 
>> 
>> 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.
>> 
>> hh
>> 
>> _______________________________________________
>> swift-server-dev mailing list
>> swift-server-dev at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-server-dev