Depending on the which connection types and which protocols are in use,
file transfer implementations
( GridFtp, SSH, FTP )
and Streaming Data implementations
( WebServices for put and get Files, Upload Servlet, Client Polling )
provide a number of opportunities to hook the process to a standard XML Transform Factory.
Server-side dispatch threads running CDC Commands
mid-left hand side for dispatcher
required for each subscription
utilize translations after retreiving them from the subscription's propertySet in order to return only the DOM Element List required by that user on the data for that Topic.
Client-side translations can be manually controlled and tweaked on the subscribers site
via command line arguments used to
start the Polling Console
as explained in
Examples Run Demo Track 3 and the property for
Server-side XML translations depicted in the lower right-hand side of the Process Subscriptions OOA OOD Model Refer to the diagrams objects in the list:
Xml Translation Process details below:
Remember that every Subscription to a topic is represented by a
Channel Data Command ( CDC ) that encodes for both the connection's properties
and the command to actually move data on the connection.