On 08 Jan 17  11:44:32, Mark Lewis said the following to Nick Andre:   
      
   ML> i remember the different dup cache files... i didn't know they were limited   
   ML> a paltry 1024 entries, though... i never dug that deep ;)   
      
   1024 may not seem like much, but as I explained about how dupe detection works   
   in DB it actually is sufficient. Again... if anyone didn't think it was, I    
   would've heard about it by now and increased it.   
      
   ML>  NA> Interestingly it appears that there is a "reputation" method for the   
   ML>  NA> cache database. It appears as it is loaded into RAM during a toss, any   
   ML>  NA> time a CRC match is encountered, that CRC is pushed up the cache   
   ML>  NA> table, while CRC's of legitimate messages end up being pushed down.   
   ML>  NA> The CRC table is saved into that cache file every time the Echomail   
   ML>  NA> area changes in the toss cycle; or there are no more packets to toss.   
   ML>    
   ML> that's pretty interesting... i guess that's so that messages with more dupe   
   ML> can be detected faster with their CRCs at the top of the queue... interesti   
   ML> idea and i'm sure one that was important back in the day of slower machines   
      
   That sounds about correct, D'Bridge was written with PC/XT in mind. There was    
   a bunch of caching code for the Echomail database at one time; which I had to    
   remove as it limited the total areas a Sysop could have. One could argue that    
   a DOS computer like the XT's or Tandy 1000's could just install Norton    
   Speedcache or even Smartdrive but that would just take away from available    
   conventional memory/heap. The size of the mailer's configuration also takes   
   away from conventional memory... especially the Netmail routing table.   
      
   Nick   
      
   --- Renegade vY2Ka2   
    * Origin: Joey, do you like movies about gladiators? (1:229/426)