Microsoft.AspNetCore.Connections.Abstractions

Helper code for the various activator services.

Instantiate a type with constructor arguments provided directly and/or from an .

The service provider used to resolve dependencies The type to activate Constructor arguments not provided by the . An activated object of type instanceType

Create a delegate that will instantiate a type with constructor arguments provided directly and/or from an .

The type to activate The types of objects, in order, that will be passed to the returned function as its second parameter A factory that will instantiate instanceType using an and an argument array containing objects matching the types defined in argumentTypes

Instantiate a type with constructor arguments provided directly and/or from an .

The type to activate The service provider used to resolve dependencies Constructor arguments not provided by the . An activated object of type T

Retrieve an instance of the given type from the service provider. If one is not found then instantiate it directly.

The type of the service The service provider used to resolve dependencies The resolved service or created instance

Retrieve an instance of the given type from the service provider. If one is not found then instantiate it directly.

The service provider The type of the service The resolved service or created instance

Marks the constructor to be used when activating type using .

The result of .

The to get service arguments from. Additional constructor arguments. The instantiated type.

Represents an end point that multiple connections connect to. For HTTP, endpoints are URLs, for non HTTP it can be a TCP listener (or similar)

Called when a new connection is accepted to the endpoint

The new A that represents the connection lifetime. When the task completes, the connection is complete.

Creates the DefaultConnectionContext without Pipes to avoid upfront allocations. The caller is expected to set the and pipes manually.

Indicates if the connection transport has an "inherent keep-alive", which means that the transport will automatically inform the client that it is still present.

The most common example of this feature is the Long Polling HTTP transport, which must (due to HTTP limitations) terminate each poll within a particular interval and return a signal indicating "the server is still here, but there is no data yet". This feature allows applications to add keep-alive functionality, but limit it only to transports that don't have some kind of inherent keep-alive.