judo-runtime:dispatcher-architecture

The JUDO Dispatcher routes incoming requests to the correct handlers—behavior, script, or SDK—based on the operation type. This ensures that each request is processed by the appropriate handler within the architecture, enabling accurate execution and debugging of custom flows.

To implement a custom interceptor for pre-processing requests, you need to understand the JUDO Dispatcher's extension points and interceptor flow. The architecture provides specific handler mechanisms that allow you to inject custom logic into the request lifecycle before it reaches the target operation.

Context management in the JUDO Dispatcher involves maintaining thread context, resolving variables, and managing actor information throughout the request flow. This ensures that all handlers and interceptors have access to the correct contextual data during execution.

The transaction lifecycle in the JUDO Dispatcher is managed alongside the interceptor flow, ensuring that operations are executed within a controlled transactional boundary. This allows for proper state management and rollback capabilities if the operation routing or behavior handling fails.

Yes, the JUDO Dispatcher provides extension points for custom variable providers, allowing you to inject specific variables into the resolution context. This is particularly useful for advanced debugging and customizing how the thread context and actor information are handled during request processing.

When modifying the DefaultDispatcher for custom behavior handling, you are constrained by the existing interceptor flow and context management rules. Care must be taken to ensure that any custom handlers or variable resolvers do not disrupt the standard transaction lifecycle or operation routing.