Description: Here's some stuff I've been working on that has hit a reasonable stopping point.
Splitting the "Handler" codebase into two different handler styles for different use cases
ContextHandler base class for usage in "Chain of Handlers" pattern. Each handler is expected to do something and modify the context before handing it off to the next. Success/failure is determined by properties in the context at the end of the chain.
ReturningHandler base class for usage in "Chain of Responsibility" pattern. Only one handler is expected to fully process the input parameters and return something.
Reimplement the transport creation handler to have its own chain of responsibilities. One handler for each type of protocol to try. This implements trying shared memory, then tcp, then named pipes, then failure. Although the other two handlers will either pass or throw, they're mostly placeholders for now.
Improvement to cancelling TCP via cancellation token.
Description: Here's some stuff I've been working on that has hit a reasonable stopping point.
ContextHandlerbase class for usage in "Chain of Handlers" pattern. Each handler is expected to do something and modify the context before handing it off to the next. Success/failure is determined by properties in the context at the end of the chain.ReturningHandlerbase class for usage in "Chain of Responsibility" pattern. Only one handler is expected to fully process the input parameters and return something.Testing: See above