-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Framing - Variable size length fielded protocol #133
Conversation
Dispose LoggerFactory instances in the Client Sample app.
The "Connected to LocalEndPoint" message changed to "Connected to RemoteEndPoint", since the client is connecting to the server.
Dispose LoggerFactory
Fix connection message
Add CompleteAsync and CancelPending to the Protocols.
Update the Custom protocol to show how to disconnect the client from …
Update NuGet packages.
…ramework into UpdateCustomProtocol
Add cancel and complete
Update custom protocol
@davidfowl I'm sure you're super busy and don't have much time taking care of the PRs and issues. I really admire your works and this framework. I'd like to use this framework in a project in January, and this PR is especially important for me in order to suit for my needs. So I would be grateful, if we could sort this PR out relative quickly, so I don't have to deviate to much from your branch. Thank you! |
Fix "Feature 'target-typed object creation' is not available in C# 8.0." error.
Fix : CS1503 - Argument 1: cannot convert from 'System.Buffers.ReadOnlySequence<byte>' to 'byte[]'
Added ReadOnlyMemory<byte> constructor
Fixes #132
Added a framing protocol for a scenario when a frame is variable sized and the header's
PayloadLength
field is used to split the incoming stream. Plus implemented a sample client and server for this protocol.