February 2002
Beginner to intermediate
544 pages
10h 23m
English
A Topic object encapsulates a provider-specific topic name. It is the way a client specifies the identity of a topic to JMS API methods.
Many publish/subscribe (pub/sub) providers group topics into hierarchies and provide various options for subscribing to parts of the hierarchy. The JMS API places no restriction on what a Topic object represents. It may be a leaf in a topic hierarchy, or it may be a larger part of the hierarchy.
The organization of topics and the granularity of subscriptions to them is an important part of a pub/sub application's architecture. The JMS API does not specify a policy for how this should be done. If an application takes advantage of a provider-specific topic-grouping ...
Read now
Unlock full access