Protocol Methods

Clean up the usage of controllers for the connection

Makes sure that there is an instance of a specific controller. Also makes sure that security is in place. Knowing what methods the connection can call.

Determines whether the specified object is equal to the current object.

Invoke the correct RPC controller/method with the payload. Also handles return values when needed

Invoke the correct RPC controller/method with the payload. Also handles return values when needed Will execute 1 operation at the time. Other operations will wait. This will be executed when the IController or the method being invoked is decorated with the RunSynchronouslyAttribute

Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.

Flushes the IBaseTransport write stream

Creates a ControllerDelegate to use when calling the controller/method

Sent to clients when ping has failed more times than allowed

Serves as the default hash function.

Each protocol is responsible for returning a valid ping frame for that protocol

Gets the Type of the current instance.

True if the controllers repository has a instance of the specific BinaryKey

Setup the properties on the ClientStats object

Creates a shallow copy of the current Object.

Each protocol should implement a read loop

Removes a controller instance from the Controllers repository.

Enqueue the data to send and update the IServerStatistics

Each protocol is responsible for building the message to send

Send loop that reads the OutQueue

If heartbeat is enabled on this endpoint the method will initiate a ping/pong sequence

Returns a string that represents the current object.