Subj : *.MSG vs. packed help?
To : Mike Luther
From : Jonathan de Boyne Pollard
Date : Tue Jul 10 2001 12:35 am
ML> But what is missing, if I go to, for example SQUISH and a SQUISH
ML> message base, is the fact that in the toss process, we don't get a
ML> new cap and a new stack of *.MSG's in a directory to clue the askSam
ML> thread task, to "Aha! traffic! Munch in all from the old cap to the
ML> new one!" That's how I wrote the interface code hard coded untility
ML> which is called now to do the task I wrote ass MSG2ASK.EXE all these
ML> years ago.
Am I to gather than the problem is not the SQUISH messagebase format, but the
triggering of the scan itself ?
Why not trigger it with the same mechanism that you use to trigger SQUISH ? At
some point you know when to run the tosser. So just before you run the tosser,
make copies of the ARCmail and *.PKT files, decompress them, convert the
contents to "askSam" format, and import them into the database.
An alternative, and very different, approach is to essentially have a purpose
designed "scanner", that maintains its own set of "last read" pointers for each
area in your messagebase. When run, it scans each area, updating the last read
pointers as it goes, exporting newly entered messages from the messagebase into
the "askSam" database. All that you then need do is trigger it whenever
something new is added to your messagebase, or simply run it at regular
intervals.
� JdeBP �
--- FleetStreet 1.22 NR
* Origin: JdeBP's point, using Squish <yuk!> (2:440/4.3)
