* MHonArc should understand most non-numeric timezones. May need some education. Logs show MHonArc is ignorant of AEST, MET; no errors reported under fukuzawa. See <TIMEZONE> resource.
* A single clock incorrectly set far in the future can do very large damage. More than enough to offset the gains of Date: indexing. * Agree, a multi-index solution may be a good way to go for medium term. (If benefit outweighs cost) * This is the type of issue the relational database folks love (like www.reference.com) where they can let the archive viewer decide stuff like this. Jeff
