IProtocol abstraction / Application facing interface

is there a common pattern to express HttpApplication, MqttApplication and others?

for me it is about transforming IDuplexPipe to IProtocol. What I think of is:

public interface IProtocol<TRequest,TResponse>
  {
    ChannelReader<TRequest> Input { get; }
    ChannelWriter<TResponse> Output { get; }
  }

public interface IProtocol<TMsg> : IProtocol<TMsg,TMsg>
  {
  }

[davidfowl]

nice move on moving it to nuget, I’m using it in a project I just started a couple of weeks ago https://github.com/MithrilMan/MithrilShards specifical implementation at https://github.com/MithrilMan/MithrilShards/tree/master/src/MithrilShards.Network.Bedrock

Nice!! I need to iterate on the interface a bit since it forces allocations today. There needs to be a protocol reader interface that either returns a disposable or has an Advance method on it. I hope to get feedback for this.

As a note, I think would be nice to have an explicit method to override from ConnectionHandler to catch peer disconnection, so other than public abstract Task OnConnectedAsync(ConnectionContext connection); we should have a public abstract Task OnDisconnectedAsync(ConnectionContext connection, Exception ex);

This could be built on top. Right now the lowest level is basically a single call and when that task completes.

good job on this library, is it planned to be merged into next dotnet core release somehow?

Thanks! This is my playground to figure out what is useful to people. I’m not sure if all of it will make it into .NET Core but hopefully some of the core abstractions will at some point.

[JanEggers]

thx for letting me know. and have nice holidays