The runtime infrastructure seems significantly complicated by the
fact that we support invocation chains of both around-style
interceptors and "one-way" message handlers. I propose we simplify
this by going just with around-style interceptors. With this
approach, outgoing and callback invocation chains will just be
composed of interceptors. This will greatly reduce the ugliness in
ConnectorImpl as well as make re-wiring, data transformation, adding
policy, and wire post-processing more straightforward. Since we now
have a representation of operations, it is possible for policy
builders to determine at build time whether or not to supply a non-
blocking interceptor. In the case of a non-blocking interceptor,
after it calls next to continue processing down the pipeline, it must
simply return as any callback response will be sent down the
callback invocation chain. For synchronous calls, interceptors could
maintain state on the stack. This of course means we will have to be
careful to supply a timeout mechanism for thread dispatching but that
can be done in the work scheduler.
If there are no objections, I would like to do this after Ignacio
commits his patch for composite wiring next week.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
