Skip to content
This repository was archived by the owner on Dec 18, 2018. It is now read-only.

Rationalize IConnection and ConnectionContext #1892

Description

@davidfowl

This is the last remaining piece of work to do from #1453.

The cheapest solution I see is to:

  • Implement ConnectionContext on the HttpConnection
  • Introduce IConnectionFactory to the HubConnection layer
public IConnectionFactory
{
    Task<ConnectionContext> ConnectAsync(TransferFormat transferFormat);
}

The last thing to figure out after that would be how we do DisposeAsync (it could be Abort), see aspnet/KestrelHttpServer#2054

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions