public static interface TopicControl.MissingTopicNotification
Processing of the initial request will be halted until proceed
is called, at which point the selector will be resolved against
the topic tree again.
If after calling proceed
the selector still does not
match against any topics, no further notifications will be provided.
Should cancel
be called, or the notification time out,
the request will be discarded. The requesting session will not be
notified that their request has been cancelled.
Modifier and Type | Method and Description |
---|---|
void |
cancel()
Cancel the client request on the server.
|
SessionId |
getSessionId()
Returns the identity of the client session that made the request.
|
String |
getTopicPath()
Returns the topic path derived from the requested topic selector.
|
TopicSelector |
getTopicSelector()
Returns the
TopicSelector that triggered this notification. |
void |
proceed()
Instruct the server to complete processing of the session request.
|
SessionId getSessionId()
String getTopicPath()
getTopicSelector().getPathPrefix()
.TopicSelector getTopicSelector()
TopicSelector
that triggered this notification.void proceed() throws SessionClosedException
This may be called after additional operations (such as adding topics) have been performed, to allow the requested selector to be resolved against the updated topic tree.
For subscription requests, the topic selector will be added to the client's topic selections. This will cause the client session to become subscribed to topics that match the selector if they are added later.
SessionClosedException
- if the local session is closedvoid cancel() throws SessionClosedException
Calling this will prevent any further processing of the request. For subscription requests, the topic selector will be discarded. The client session will not become subscribed to topics that match the selector if they are added later.
SessionClosedException
- if the local session is closedCopyright © 2016 Push Technology Ltd. All Rights Reserved.