On Thu, 10 Jul 1997 09:56:06 +1000 (EST), proff@suburbia.net wrote: >> Other than different servers having different article id's, what >> limitations would prevent NNTPCache from doing this (if it doesn't)? > >The different article id's is unfortunately a problem that can't >be resolved. Infact nntpcache goes to quite some lengths to avoid >article ID collisions even in the normal case i.e for crossposts >to the same group from different servers. It's a significant problem, but few things with computers fall under "can't". It would mean that for every group scanned, the server would have to download the message ids of every article in each parent server and keep it's own history database (with multiple possible article sources (which local article #, server1/article#, server2 article #, etc...), and it's own active file not based on the cached servers. This would be significantly more complicated programming and probably generate a little more traffic then it does now, but still far less traffic, and far less storage, and a smaller history then a full load generates.... If this option existed, I would prefer it... I'm too low on time and realatively happy with NNTPCACHE as it's delivered now, but if someone gives me $20,000.00 I could be convienced to patch this into NNTPCACHE.. ;-)
