Skip to content

TopicUnsubRequest

Purpose

Unsubscription request for a pub/sub topic.

Type

Reception:

TopicUnsubRequestV1

Record with fields:

Pub/sub topic identity

Whether the unsubscription request is local-only or should be also sent to the network

Triggers:

TopicUnsubResponseV1

Result

Structure

Field Type Description
topic TopicIdentity Topic ID to unsubscribe
scope RoutingScope Whether the unsubscription request should be sent to the network

Behaviour

If the topic does not exist yet in the RoutingTable, the EngineIdentity of the requesting engine is added to the RoutingTable, and a TopicSubResponse is returned with a success result.

Otherwise, if the topic does not exist yet:

Message flow

sequenceDiagram

%% --8<-- [start:sequence]
Any Local Engine ->>+ Router: TopicUnsubRequest
Router ->>+ PubSub: UnsubscribeRequest
PubSub -->>- Router: UnsubscribeResponse
Router -->>- Any Local Engine: TopicUnsubResponse
%% --8<-- [end:sequence]
(Wiki) links on this page