...

• All specified interceptors are guaranteed to be executed before calling the service method.
• Listeners are notified asynchronously.
• The server interceptor binds to the service itself (it must be executed where the service is implemented, if on Java then in Java, if on Net then in Net).
• The client interceptor binds to the proxy invocation handler. In fact, the main task of the client interceptor is to transfer the parameters of the caller to the service instance (using the RequestContext).
• If the interceptor throws an exception, the service method is not executed, but the rest of the interceptors are executed. This exception is passed to the user and to the listeners.
• Any interceptor can change the RequestContext.
• RequestContext must be accessible inside the service(?).

Example of usage diagram

draw.io Diagram
border true diagramName middleware simpleViewer false width links auto tbstyle top lbox true diagramWidth 1001 revision 4

Risks and Assumptions

// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.

...