Package dev.tachyonmcp.core.server

Class OutboundSseStreamMessageRouter

java.lang.Object

dev.tachyonmcp.core.server.OutboundSseStreamMessageRouter

All Implemented Interfaces:

OutboundStreamResolver

@InternalApi
public final class OutboundSseStreamMessageRouter
extends Object
implements OutboundStreamResolver

Default OutboundStreamResolver that diverts events through an OutboundSseStream bound in the current dispatch context when the dispatch session matches the target session. Otherwise, lets the caller fall through to the normal GET-SSE path.

Constructor Summary

Constructors

Constructor	Description
OutboundSseStreamMessageRouter()

Method Summary

Modifier and Type	Method	Description
static @Nullable OutboundSseStream	currentOutboundSseStream()
static @Nullable String	currentSessionId()
@Nullable OutboundSseStream	resolve(Session session)	Resolves the OutboundSseStream bound in the current dispatch context for the given session, if any.
static <T> T	withDispatchContext(@Nullable String sessionId, @Nullable OutboundSseStream outboundSseStream, Callable<T> action)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

OutboundSseStreamMessageRouter

public OutboundSseStreamMessageRouter()

Method Details

withDispatchContext

public static <T> T withDispatchContext(@Nullable String sessionId,
 @Nullable OutboundSseStream outboundSseStream,
 Callable<T> action)
                                 throws Exception

Throws:

Exception

currentOutboundSseStream

public static @Nullable OutboundSseStream currentOutboundSseStream()

currentSessionId

public static @Nullable String currentSessionId()

resolve

public @Nullable OutboundSseStream resolve(Session session)

Description copied from interface: OutboundStreamResolver

Resolves the OutboundSseStream bound in the current dispatch context for the given session, if any. The caller needs the stream before building the event (its OutboundSseStream.streamKey() goes into the SSE event id and the event log), so resolution and delivery are separate steps.

Specified by:

resolve in interface OutboundStreamResolver

Parameters:

session - the target session for the event

Returns:

the bound stream to deliver on, or null to fall through to the session's GET-SSE connection