Specify from users point of view destination queue for message;
implicity uses internally a TopicObject DTD
But DestinationObject inherits from TreeObject
List of Entities for which one wishes to direct some information
This can be explicit names or implicitly defined either a
selector or by Topic of Publish/Subscribe system
Specify list of destination objects using DestinationObject DTD
Allows multiple destinations and implies DestinationQueue,
DestinationTopic, DestinationSubTopic
Used in cruder JMS Header specification of Destination
Stream to which event belongs in full InternalND Syntax
//GarnetRoot/B/C/ ../Streamitself
This is ESSENTIAL information as uniquely determines
VirtualEnvironment Sharedlet (collaborating application) and
SourceDevice and EventUserObject
Optional Specification of one or more external locations where
we might be able to find information to understand more
about GXOS Specification of This TreeObject and its related
quantities.
Source of Phase 2 Material -- Typically ProcessingRecord from
Phase 1 or Playlist Specification CustomType of Phase2Source is
either Phase1Export or Playlist
Collection (of messages) wrt to which Priority refers
If message defines a MeetingContext, default value is
GarnetRoot; if message is internal to a stream, default value is
StreamName
If message inside a MeetingContext but outside a stream, then
PriorityScope is defaulted to MeetingContextName
PriorityScope can reference any root or node of any tree
containing this message -- see TreeObject DTD
Idea is that subsystem setting Priority only has "visibility" a
certain way up the tree from where it sits
In particular, it may only know about the Sharedlet(Stream) or a
little broader the MeetingContext from which message comes from
The assumption is that "system" can apply a relative priority
between different PriorityScope's
Sharedlet GXOS Object
Currently this has no special properties
One defines a single original version of each Sharelet in
Capabilities part of GXOS
These are linked as Sharelet instances on each
VirtualEnvironment using this application
Client or Server Computer that produced message with InternalND
pointer to it as a DeviceObject
Generates SourceName SourceDomain used in JMS
This is not really necessary as implied by GMSStream and
Information available from GXOS