Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2008-10-30 05:44:54 →
Size: 1761
Editor: DannyCheung
Comment:
← Revision 2 as of 2008-10-31 04:43:04 → ⇥
Size: 2206
Editor: DannyCheung
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Sends data between two sites, usually a branch computer and the HO server.
Polling consists of several programs working in unison to create, filter and process data to a store. The programs are controlled by commin. The parameters used with the programs are accessed/altered by comaad.		 Sends data between two sites, usually a branch computer and the HO server. Polling consists of several programs working in unison to create, filter and process data to a store. The programs are controlled by commin. The parameters used with the programs are accessed/altered by comaad.

== General Polling Process ==
 1. Transaction or File Maintenance record is created/altered
 1. Transaction or File Maintenance record changes are saved to a file
 1. File is filtered for certain transaction/record types
 1. File is sent to peer
 1. Peer filters file for certain transaction/record types
 1. Peer adds transaction/record changes into it's own database
Line 5: Line 12:
When a new file maintenance record is added, a copy of the record (along with some extra information) will be placed in the "logfile" (log.dat). When you delete a record, an entry in the logfile will also be created.
Altering a file maintenance record will create two entries in log.dat. One will be a snapshot of the record before the change and the other will be a copy of the record after the change.
 1. XXaad creates entry(s) in log.dat
 1. logmin reads entries from log.dat and only outputs certain record types into slog.dat. Effectively, logmin acts as a filter.		 When a new file maintenance record is added, a copy of the record (along with some extra information) will be placed in the "logfile" (log.dat). When you delete a record, an entry in the logfile will also be created. Altering a file maintenance record will create two entries in log.dat. One will be a snapshot of the record before the change and the other will be a copy of the record after the change.

 1. {{{XXaad}}} creates entry(s) in log.dat
 1. {{{logmin}}} reads entries from log.dat and only outputs certain record types into slog.dat. Effectively, {{{logmin}}} acts as a filter.
Line 10: Line 17:
 1. On the other end, logmin reads certain entries from slog.dat and outputs it to anothter file
 1. On the other end, XXaad processes output file and applies changes.		  1. On the other end, {{{logmin}}} reads certain entries from slog.dat and outputs it to another file
 1. On the other end, {{{XXaad}}} processes output file and applies changes.
Line 13: Line 20:
 1. XXeat creates an entry in daytrn.dat
 1. sen2post copies the entries from daytrn.dat, adds a bit of extra information and outputs it to sendtrn.dat
 1. sendpost reads sendtrn.dat and outputs certain transactions to rsndtrn.dat		  1. {{{XXeat}}} creates an entry in daytrn.dat
 1. {{{sen2post}}} copies the entries from daytrn.dat, adds a bit of extra information and outputs it to sendtrn.dat
 1. {{{sendpost}}} reads sendtrn.dat and outputs certain transactions to rsndtrn.dat
Line 17: Line 24:
 1. On other computer, sendpost reads in rsndtrn.dat, filters transactions and outputs to sendtrn.dat
 1. On other computer, reclstr converts sendtrn.dat to daycomm.dat, which just a strucutrally the same as daytrn.dat
 1. On other computer, XXpost will now add transactions to its transaction history file		  1. On other computer, {{{sendpost}}} reads in rsndtrn.dat, filters transactions and outputs to sendtrn.dat
 1. On other computer, {{{reclstr}}} converts sendtrn.dat to daycomm.dat, which just a structurally the same as daytrn.dat
 1. On other computer, {{{XXpost}}} will now add transactions to its transaction history file
Line 21: Line 28:
 CategoryPolling  . CategoryPolling

Polling

Sends data between two sites, usually a branch computer and the HO server. Polling consists of several programs working in unison to create, filter and process data to a store. The programs are controlled by commin. The parameters used with the programs are accessed/altered by comaad.

General Polling Process

  1. Transaction or File Maintenance record is created/altered
  2. Transaction or File Maintenance record changes are saved to a file
  3. File is filtered for certain transaction/record types
  4. File is sent to peer
  5. Peer filters file for certain transaction/record types
  6. Peer adds transaction/record changes into it's own database

Polling File Maintenance Records

When a new file maintenance record is added, a copy of the record (along with some extra information) will be placed in the "logfile" (log.dat). When you delete a record, an entry in the logfile will also be created. Altering a file maintenance record will create two entries in log.dat. One will be a snapshot of the record before the change and the other will be a copy of the record after the change.

  1. XXaad creates entry(s) in log.dat

  2. logmin reads entries from log.dat and only outputs certain record types into slog.dat. Effectively, logmin acts as a filter.

  3. slog.dat is sent to the other location

  4. On the other end, logmin reads certain entries from slog.dat and outputs it to another file

  5. On the other end, XXaad processes output file and applies changes.

Transactions

  1. XXeat creates an entry in daytrn.dat

  2. sen2post copies the entries from daytrn.dat, adds a bit of extra information and outputs it to sendtrn.dat

  3. sendpost reads sendtrn.dat and outputs certain transactions to rsndtrn.dat

  4. rsndtrn.dat is sent to other computer

  5. On other computer, sendpost reads in rsndtrn.dat, filters transactions and outputs to sendtrn.dat

  6. On other computer, reclstr converts sendtrn.dat to daycomm.dat, which just a structurally the same as daytrn.dat

  7. On other computer, XXpost will now add transactions to its transaction history file

Polling (last edited 2022-04-13 03:06:32 by 203-206-72-221)