http
http copied to clipboard
:warning: Historical HTTP API - please use https://github.com/swift-server/async-http-client instead
I don't know where I can submit proposals for api changes so I opened this issue. ### HTTPServer port server port is determined in `start(port:, handler:)` method, while I think...
Noticed that we don't seem to have an official style guide that we adhere to. I think it would be nice if we could pick one as we could encode...
In #96, @helje5 noted that the number of `queues` that we use in the `HTTPServer` should be lifted up into the `Options` Just tracking that thought here.
Based on comments from @helje5: Don't do port: 0, should raise an error. Do port: nil for kernel assigned, or a real port
Determine the lifecycle of the HTTP server. Refer to the discussions from #82 for history. An initial idea discussed in that PR is: > - init: sets up the server...
See PR #20 for history. Need to revisit this after #96 is complete and we have a perf baseline.
From @helje5: https://github.com/swift-server/http/pull/81#issuecomment-342630664 An open question is, do we want to support multiple binds? I tend to say yes. This would modify the structure of the server a little. (the...
From comments by @helje5 in #81 `Port` is insufficient. We need to allow an (or many!) arbitrary `sockaddr_in` (either via sockaddr_in or a wrapper). If only to allow IPv6 and...
I've been looking through example code for the HTTP library and the use of a associated value closure for the `HTTPBodyProcessing.processBody` case feels kind of usual. I've never seen such...
The current implementation doesn't honor the `stop` flag (the `inout Bool`) in `HTTPBodyHandler`. Need to fix that and write a test for it.