### Dispatch - data collection / distribution / persistent technologies

Dispatch is a set of JavaBeans providing data collection, distribution, and persistent technologies. Data collection can be from multi sources to multi receiving stations with specific simultaneous communication channels via one-to-many, or many-to-one, or anything between. Data objects are carried by containers, which can act as an object to be collected by other containers. Data distribution can be sequentially, or simultaneously, or block sequentially with specially controlled events such as CustomEvent, CustomTimer to control initially delay and repeated broadcasts, PropertyChange with old and new value of specific properties, and VetoableChange to trigger sets of accepted events and rejected events. Activities of these events can be logged to an object table database. Data persistent allows objects and their containers to be distributed anywhere. At each destination they are resurrected at previous states for further processing, storage, or re-distribution. Internet can act as a virtual network, where data objects have no boundary either from the sources or to destinations. Dispatch JavaBeans speaks multi languages right from the start.

Dispatch comprises:

1. Three mechanisms of object containers, carrriers, and receivers:
   - A general object container that carries Serializable objects, and acts as a common receiver to collect other dispatched containers of its own kind. Each contained object has an id tag.
   - A structured-data container, where object is identified by its own name having all functions of a general object container, plus features for setting data record structure and data entry to guarantee the intergrity of a data record: each record has the same number of fields, and data in each field of all records belong to the same class. Data record can be multi point distributions and collections.
   - An object database in table format, with or without a primary key index constructed from one or many fields. The table can receive both distributed records of structured data container, and distributed tables of its own kind. It plays both roles as a receiving station from many sources, and as a carrier to many destinations.

2. Five mechanisms of distribution services:
   - A general information dispatcher that can deliver each round up to 8 Serializable attachements to update up to 8 different Listeners (receiving stations), each attachement per Listener, or 8 attachement to 1 Listener, or any combination of the two cases. A flexible synchonizing mechanism assures unique channel connection between source dispatcher and its receiving stations.
   - A CustomEvent dispatcher for notification and delivery of a message and an attachment. Its activities can be logged to a table.
   - A CustomTimer dispatcher for notification and delivery of a message and an attachment after an initial delay and repeatedly after an elapsed time, which can be different from initial delay. Its activities can be logged to a table.
   - A PropertyChange dispatcher to announce specified old and new value of a property. Its activities can be logged to a table.
   - A VetoableChange dispatcher to announce specified old and new value of a property, and response to objection of any receiver. Its activities can be logged to a table.

3. Standard persistent mechanisms via local file system, printing and multi language services.

4. Enterprise persistent mechanisms via HTTP standard Servlet / Secure Socket Layer to move data objects across Internet to Web server, from one server to another server via CORBA Internet Inter Object Protocol (IIOP), and from server to database engines.

| Teconomics Inc. 103 Edgevalley Green N.W. Calgary Alberta Canada T3A 4Y9 Phone: (403) 547-1287 Fax: (403) 239-7762
E-mail: dbgroups@dbgroups.com
Web: http://www.dbgroups.com

[ Catalog Home ]