Hi Matthias,
On 2021-05-05 09:38:25, you wrote to me:
WV>> I sometimes turn on compression for links that are offline for a bit
WV>> longer then 1 or 2 days. Because with the high frequent tossing that
WV>> happens today, the outbound directories quickly fill up with hundreds
WV>> of .pkt files, which I don't like. With compression turned on there
WV>> are at most 7 files for each (offline) node waiting to be send. When
WV>> they become connectable again I turn compression back off...
MH> That's a nice idea, but forces manual intervention in most cases.
Indeed. That's why I use the threshold of 1 or 2 days. Most connection problems are solved within that period.
MH> Packed echomail is a bad idea with the high frequenies as one will
MH> run out of file extensions after 36 polls. (.WE0-9 + .WEA-Z).
It could indeed. My tosser just keeps using the Z if that's reached. Which doesn't seem to cause problems, as far as I'm aware of...
MH> Having unpacked for offline systems is a pain in the outbound, but
MH> having compressed for active nodes is a pain as well.
MH> My solution: uncompressed & not looking in the outbound too often.
That works too! ;)
Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)
|