David Fowler
David Fowler
That's correct. The current abstractions are for streaming, connection based transports.
Iād need to understand more about the goals. What does the proposed API look like? The current API are for a stream based abstraction, not message based.
> Got rid of SequenceReader in WebSocketFrameReader and optimized some of the sync ValueTask paths in WebSocketMessageReader to avoid some state machine creation. More to do there. Would be good...
https://github.com/davidfowl/BedrockFramework/issues/20
Next year or 2 š
This logic: ``` var token = connection.ConnectionClosed.Register(() => { DisposeConnection(connection, reader, writer).ConfigureAwait(false); }); ``` Is broken. Get rid of it. The system will dispose the connection and clean up when...
Why?
I had to look again because some of these options don't let quit, they run forever. This is only useful for rabbit mq right?
@adamradocz Have you been using bedrock? I'd love to hear how, these PRs are great. I'm going to find some time to go through them.
Yes please, send the fix.