[swift-server-dev] Next HTTP API meeting

Michael Chiu hatsuneyuji at icloud.com
Mon Mar 27 09:54:17 CDT 2017

Actually according to @hh, the compiler will add the synchronization overhead no matter what.

My guess is, despite the fact that the response will always been processed by the same thread, but there'll be always a reference back to the main event loop, and it is not obvious to the compiler so it will add the overhead anyways, probably not lock but compare and swap.

Sent from my iPhone

> On Mar 27, 2017, at 7:42 AM, Tanner Nelson <tanner at qutheory.io> wrote:
> @chris in my experience there's been very little passing of request/response between threads. Usually the server accepts, spins up a new thread, and all HTTP parsing/serializing happens on that one thread. 
> Could you specify some examples where requests/responses are being passed between threads?
> That said, it should be fairly easy to implement threading to see what the effects would be. I will look into that. :)
> Tanner

More information about the swift-server-dev mailing list