David Fowler

cc @pakrym

Implement OpenSSL based TLS support

6

Details here need to be fleshed out and I'm going to lean on @Drawaes to help flesh this out and break it down into work items. Ideally we'd have several...

Unify server and client socket transport

3

The socket transport on the server side is the one used in Kestrel by ASP.NET Core. It's optimized to not allocate and has a memory pool that uses pre-pinned buffers...

Implement HTTP/1.x IMessageReader and IMessageWriter

15

We should have a well tested blazing fast implementation of the various HTTP/1.x parsers: ## Server - [ ] - Decide on the representation for an HTTP request and body...

Once we have an HTTP implementation that we like, we should enter the benchmarks.

Proposal: IMessageReader<T> TryParseMessage overload with SequenceReader<byte>

2

Today `IMessageReader` looks like this: ```C# public interface IMessageReader { bool TryParseMessage(in ReadOnlySequence input, ref SequencePosition consumed, ref SequencePosition examined, out TMessage message); } ``` This works when the caller...

There's a prototype of the [NamedPipeTransport](https://github.com/davidfowl/BedrockFramework/tree/d25d5b37ad071f55f248d28307196a0defbeb162/src/Bedrock.Framework.Experimental/Transports/Pipes) in the experimental project. We'd like to move this over to the main project but it needs to be cleaned up and tested to...

Improve performance of ProtocolReader

5

There are a few things that can be done to improve the performance of the ProtocolReader: - [x] - Store the last ReadResult from the PipeReader and synchronously parse the...

I happened to be reading this and came across the _High performance parser for the Redis protocol_ section. https://redis.io/topics/protocol It might be interesting to re-work the existing parsing to match...