Interface and Description |
---|
com.pushtechnology.diffusion.client.features.control.clients.AuthenticationControl.ControlAuthenticationHandler
since 6.2
ControlAuthenticationHandler has been replaced by the
|
com.pushtechnology.diffusion.client.security.authentication.AuthenticationHandler
since 6.2
AuthenticationHandler has been replaced by the
|
com.pushtechnology.diffusion.client.security.authentication.AuthenticationResult
since 6.2
This interface is used by |
com.pushtechnology.diffusion.client.security.authentication.AuthenticationResultSource
since 6.2
This interface is used by |
com.pushtechnology.diffusion.client.details.ClientLocation
since 6.2
Session details are only used by |
com.pushtechnology.diffusion.client.details.ClientSummary
since 6.2
Session details are only used by |
com.pushtechnology.diffusion.client.content.Content
since 6.2
This interface is preserved only for backwards compatibility and
is being phased out in favor of specific data types. The only
remaining places where it must be used are in some of the
|
com.pushtechnology.diffusion.client.features.ContextStream
since 6.2
This is only used by |
com.pushtechnology.diffusion.client.features.Messaging.MessageStream
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.Messaging.SendCallback
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.Messaging.SendContextCallback
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.MessageHandler
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.MessageHandlerStream
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.SendCallback
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.SendContextCallback
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.SendToFilterCallback
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.SendToFilterContextCallback
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.types.ReceiveContext
since 6.2
This is only used within one-way messaging, which is deprecated from this release. This interface will be removed in a future release. |
com.pushtechnology.diffusion.client.topics.details.RoutingTopicDetails
since 6.0
The use of |
com.pushtechnology.diffusion.client.types.SendOptions
since 6.2
This is only used within one-way messaging, which is deprecated from this release. This interface will be removed in a future release. |
com.pushtechnology.diffusion.client.details.SessionDetails
since 6.2
Session details are only used by |
com.pushtechnology.diffusion.client.topics.details.SlaveTopicDetails
since 6.0
The use of |
com.pushtechnology.diffusion.client.features.Stream
since 6.2
This is only used by |
com.pushtechnology.diffusion.client.features.control.topics.TopicControl.TopicEventListener
Since 6.1
See
|
com.pushtechnology.diffusion.client.features.control.topics.TopicControl.TopicEventStream
Since 6.1
See
|
com.pushtechnology.diffusion.client.topics.details.TopicDetails
since 6.0
The use of |
com.pushtechnology.diffusion.client.features.Topics.FetchContextStream
since 6.2
See |
com.pushtechnology.diffusion.client.features.Topics.FetchStream
since 6.2
See |
com.pushtechnology.diffusion.client.features.Topics.TopicDetailsCallback |
com.pushtechnology.diffusion.client.features.Topics.TopicDetailsContextCallback |
com.pushtechnology.diffusion.client.features.control.topics.TopicUpdateControl
since 6.2
|
Class and Description |
---|
com.pushtechnology.diffusion.client.security.authentication.CompositeAuthenticationHandler
since 6.2
|
com.pushtechnology.diffusion.client.features.control.clients.CompositeControlAuthenticationHandler
since 6.2
|
Enum and Description |
---|
com.pushtechnology.diffusion.client.features.control.clients.MessageQueuePolicy.ThrottlerType
since 6.3. Per-session throttling has been deprecated in
favor of the new per-topic throttling capabilities provided
by
topic views . This class will be removed
in a future release. |
Method and Description |
---|
com.pushtechnology.diffusion.client.features.Messaging.addFallbackMessageStream(Messaging.MessageStream)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.addMessageHandler(String, MessagingControl.MessageHandlerStream, String...)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.addMessageHandler(String, MessagingControl.MessageHandler, String...)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.Messaging.addMessageStream(String, Messaging.MessageStream)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.Messaging.addMessageStream(TopicSelector, Messaging.MessageStream)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.TopicControl.addTopicEventListener(String, TopicControl.TopicEventListener)
since 6.1
The main use case for this method is the removal of unused
topics, now much better satisfied by the
|
com.pushtechnology.diffusion.client.features.control.topics.TopicControl.addTopicEventListener(String, TopicControl.TopicEventStream)
since 6.1
The main use case for this method is the removal of unused
topics, now much better satisfied by the
|
com.pushtechnology.diffusion.client.Diffusion.authenticationResult()
since 6.2
|
com.pushtechnology.diffusion.client.features.Topics.fetch(String, C, Topics.FetchContextStream<C>)
since 6.2
Prefer the use of |
com.pushtechnology.diffusion.client.features.Topics.fetch(String, Topics.FetchStream)
since 6.2
Prefer the use of |
com.pushtechnology.diffusion.client.features.Topics.fetch(TopicSelector, C, Topics.FetchContextStream<C>)
since 6.2
Prefer the use of |
com.pushtechnology.diffusion.client.features.Topics.fetch(TopicSelector, Topics.FetchStream)
since 6.2
Prefer the use of |
com.pushtechnology.diffusion.client.types.SendOptions.getHeaderList()
since 6.0
The use of headers on messages will be removed in a future release. |
com.pushtechnology.diffusion.client.features.control.clients.MessageQueuePolicy.getThrottlerType()
since 6.3. Per-session throttling has been deprecated in
favor of the new per-topic throttling capabilities provided
by
topic views . This method will be removed
in a future release. |
com.pushtechnology.diffusion.client.features.control.clients.MessageQueuePolicy.getThrottlingLimit()
since 6.3. Per-session throttling has been deprecated in
favor of the new per-topic throttling capabilities provided
by
topic views . This method will be removed
in a future release. |
com.pushtechnology.diffusion.client.features.Topics.getTopicDetails(String, TopicDetails.Level, C, Topics.TopicDetailsContextCallback<C>)
since 6.0
The use of |
com.pushtechnology.diffusion.client.features.Topics.getTopicDetails(String, TopicDetails.Level, Topics.TopicDetailsCallback)
since 6.0
The use of |
com.pushtechnology.diffusion.client.types.SendOptions.Builder.headers(List<String>)
since 6.0
The use of headers on messages will be removed in a future release. |
com.pushtechnology.diffusion.client.features.Messaging.removeMessageStream(Messaging.MessageStream)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. See |
com.pushtechnology.diffusion.client.features.control.topics.TopicControl.removeTopicsWithSession(String)
since 6.1
The preferred method for automatic removal of topics is
the
To achieve a dependency upon more than one session, a condition specifying a principal name or some other session property can be used. This method will be removed in a future release. |
com.pushtechnology.diffusion.client.features.control.topics.TopicControl.removeTopicsWithSession(String, TopicTreeHandler)
since 6.1
The preferred method for automatic removal of topics is
the
To achieve a dependency upon more than one session, a condition specifying a principal name or some other session property can be used. This method will be removed in a future release. |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, Bytes)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, Bytes, C, MessagingControl.SendContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, Bytes, MessagingControl.SendCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, Bytes, SendOptions)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, Bytes, SendOptions, C, MessagingControl.SendContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, Bytes, SendOptions, MessagingControl.SendCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, CharSequence)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, CharSequence, C, MessagingControl.SendContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.send(SessionId, String, CharSequence, MessagingControl.SendCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, Bytes)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, Bytes, C, Messaging.SendContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, Bytes, Messaging.SendCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, Bytes, SendOptions)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, Bytes, SendOptions, C, Messaging.SendContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, Bytes, SendOptions, Messaging.SendCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, CharSequence)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, CharSequence, C, Messaging.SendContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.Messaging.send(String, CharSequence, Messaging.SendCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.types.SendOptions.Builder.Factory.sendOptionsBuilder()
since 6.2
This is only used within one-way messaging, which is deprecated from this release. This method will be removed in a future release. |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, Bytes)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, Bytes, C, MessagingControl.SendToFilterContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, Bytes, MessagingControl.SendToFilterCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, Bytes, SendOptions)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, Bytes, SendOptions, C, MessagingControl.SendToFilterContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, Bytes, SendOptions, MessagingControl.SendToFilterCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, CharSequence)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, CharSequence, C, MessagingControl.SendToFilterContextCallback<C>)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.topics.MessagingControl.sendToFilter(String, String, CharSequence, MessagingControl.SendToFilterCallback)
since 6.2
One-way messaging is deprecated in favor of request-response
messaging. Use |
com.pushtechnology.diffusion.client.features.control.clients.AuthenticationControl.setAuthenticationHandler(String, Set<SessionDetails.DetailType>, AuthenticationControl.ControlAuthenticationHandler)
since 6.2
|
com.pushtechnology.diffusion.client.features.control.clients.ClientControl.setThrottled(SessionId, MessageQueuePolicy.ThrottlerType, int)
since 6.3. Per-session throttling has been deprecated in favor of
the new per-topic throttling capabilities provided by
topic views . This method will be removed in a
future release. |
com.pushtechnology.diffusion.client.features.control.clients.ClientControl.setThrottled(SessionId, MessageQueuePolicy.ThrottlerType, int, C, ClientControl.ClientContextCallback<C>)
since 6.3. Per-session throttling has been deprecated in
favor of the new per-topic throttling capabilities provided
by
topic views . This method will be removed
in a future release. |
com.pushtechnology.diffusion.client.features.control.clients.ClientControl.setThrottled(SessionId, MessageQueuePolicy.ThrottlerType, int, ClientControl.ClientCallback)
since 6.3. Per-session throttling has been deprecated in
favor of the new per-topic throttling capabilities provided
by
topic views . This method will be removed
in a future release. |
Enum Constant and Description |
---|
com.pushtechnology.diffusion.client.features.control.topics.TopicAddFailReason.INITIALISE_ERROR
since 6.1
This value is associated only with removed methods that allow the specification of an initial value when creating a topic. It will be removed in a future release. |
com.pushtechnology.diffusion.client.topics.details.TopicDetails.Level.SCHEMA
since 6.2
If used when requesting details this will
have the same meaning as |
com.pushtechnology.diffusion.client.features.control.topics.TopicAddFailReason.USER_CODE_ERROR
since 6.2
This value is associated only with removed methods that
create topic using the deprecated |
Copyright © 2019 Push Technology Ltd. All Rights Reserved.