Johannes Weiss

Provide an EventLoop latency monitoring solution

2

In SwiftNIO, it's super important to have consistently low EL latency. It's also fairly easy to monitor EL latency but it's still a fair amount of finicky code to write...

AcceptHandler closes child channel if parent channel is closed and there's no test for that

1

https://github.com/apple/swift-nio/blob/39047aec7c5a0738cba2c8381dc7703c5f02b771/Sources/NIOPosix/Bootstrap.swift#L453 This is lacking a test and we should think about whether that's exctly right anyway

rewrite the chat server example to use synchronisation that is obvious rather than the hacks we do

2

Rewrite the chat server example to use synchronisation that is obvious rather than the hacks we do. See [here](https://forums.swift.org/t/cant-get-writeandflush-to-send-bytes/43878/6).

``` public func completeWithTask(_ body: @escaping @Sendable () async throws -> Value) -> Task ``` cannot be used correctly if the EventLoop is `EmbeddedEventLoop`. We should `assert` that it isn't.

alternative == method linkage fix

2

alternative (to #139) fix for #138

Build fails in release with: ld: Undefined symbols: static (extension in SystemPackage):SystemPackage._StrSlice.== infix(A, A) -> Swift.Bool

1

Any package which depends on `swift-system` and uses the `==` on `FilePath.Component` will fail to build _in release mode_ (debug is fine). Consider this example program ```swift import SystemPackage print(FilePath("/x").lastComponent!...

#700 & #701: HTTPClient.shared a globally shared singleton & .browserLike configuration

4

Offer `HTTPClient.shared`, a global singleton `HTTPClient` that doesn't need shutdown (because it lives as long as your application). This globally shared `HTTPClient` does not accept any special configuration and uses...

HTTPClientRequest looks & feels like a value type but isn't

10

Sadly `HTTPClientRequest` contains a streamable body which is typically a reference to a (frequently) consume-once `AsyncSequence`. That means it's not actually a value type. That's a major API winkle that...

Logging contains newlines (because it uses ByteBuffer.debugDescription which IMHO it shouldn't)

11

AHC logs bytes of the HTTP connection (which is in itself questionable #689). But even if we think that's okay I don't think it should just log `ByteBuffer.debugDescription` which contains...

Add `HTTPClient.Configuration.browserLike`

7

We should add a ``` extension HTTPClient.Configuration { public static var browserLike: Self { ... } } ``` which should return an evolving configuration that's always as close as possible...