[JDEV] Route tag spec proposal..
tcharron at ductape.net
Mon Oct 11 14:22:14 CDT 1999
Quoting Colin Davis <davisfamily at mediaone.net>:
> > Err, the timezone data is regarding the node entity that made the
> > This is mostly just transports. They couldn't follow this rule, really.
> Why is this not possible in the transports? Is there to much overhead
> in storing the last time it sent a message to everyone?
Actually, this COULD be done, as it could simply look at the 'to' address,
and keep some sort of cache of the last 2,000 or so addresses it sent to, but
then what takes more time, transmitting the extra 20 characters? Guess we'll
have to find out.. ;-P It's just that it would require ALL transports to
support these lookup tables to actually HAVE the timezone data cached
properly. Not to mention, you'd lose it during a restart of the transport, and
there's no way of the upstream transport knowing that the destination transport
had to do a restart.
How's about instead of using
Good idea about cutting it down a bit, though..
<< Wanted: One decent sig >>
<< Preferably litle used >>
<< and stored in garage. ?>>
More information about the JDev