aMule Forum

English => Feature requests => Topic started by: analogue on July 28, 2005, 09:40:17 PM

Title: [REQUEST] Support for gzipped server.met
Post by: analogue on July 28, 2005, 09:40:17 PM
Hi,

On http://www.gruk.org/list.php I noticed their server.met file was gzipped and I can't use it with my Debian SID aMule. Do the CVS version of aMule supports gzipped server.met files ? If not, could you add support for it in a future release ?

I'd like to use the gruk.org list as they filter out all the fake spying servers  :))

Anyway, thanks for aMule !
Title: Re: [REQUEST] Support for gzipped server.met
Post by: Kry on July 28, 2005, 10:01:01 PM
Why don't you try :)
Title: Re: [REQUEST] Support for gzipped server.met
Post by: Vollstrecker on July 28, 2005, 10:01:27 PM
Why not just using the feature to retrieve new servers from other clients? I never had to download a server list. And for the fake server you can use ipfilter.dat.
Title: Re: [REQUEST] Support for gzipped server.met
Post by: analogue on July 28, 2005, 10:11:18 PM
Quote
Originally posted by Vollstrecker
Why not just using the feature to retrieve new servers from other clients? I never had to download a server list. And for the fake server you can use ipfilter.dat.

I did too before, but now clients and servers spread the fake RIAA servers. What good ipfilter.dat do you have ?
Title: Re: [REQUEST] Support for gzipped server.met
Post by: analogue on July 28, 2005, 10:33:42 PM
Quote
Originally posted by Kry
Why don't you try :)

I tried with today CVS, it doesn't work with a server.met.gz file.
Title: Re: [REQUEST] Support for gzipped server.met
Post by: Vollstrecker on July 28, 2005, 10:40:06 PM
I take the one from forum here, but I don't need it either, because it autoconnects only to statis servers, and that is atm only RB2.
Kry meant you could try to implement it, I think.
Title: Re: [REQUEST] Support for gzipped server.met
Post by: analogue on July 28, 2005, 11:15:30 PM
Quote
Originally posted by Vollstrecker
I take the one from forum here, but I don't need it either, because it autoconnects only to statis servers, and that is atm only RB2.
Kry meant you could try to implement it, I think.

Ok, I'll look into it if I have some time, but don't hold your breath  :]
Title: Re: [REQUEST] Support for gzipped server.met
Post by: Kry on July 29, 2005, 04:07:05 AM
No, I meant he try ;) Now we know it doesn't work. .zip files work tho. I'll take a look.
Title: Re: [REQUEST] Support for gzipped server.met
Post by: JusTiCe8 on June 01, 2006, 04:40:28 PM
I resurrect this thread, as it could be a nice feature to don't waste disk space with all files which may grows too much like that:

347604 clients.met
7370984 clients.met.BAK
80280461 known2_64.met  (77 Mb !)
38463076 known2.met  (37 Mb !)

It should be not too hard to add transparent gzip compression in CFile class.
Title: Re: [REQUEST] Support for gzipped server.met
Post by: wuischke on June 01, 2006, 05:31:13 PM
You can savely delete this files from time to time. The clients.met contains your 'debts' with others and shouldn't be too big. (and the BAK-file is just a back-up-copy, may be deleted too).
The known*.met files contain file hashes of all the files you downloaded once, you really don't need the data about the old ones, thus delete the files and let aMule rehash to have only the files you're really sharing inside.

But I agree about the gzip/bz2-thingy would be really great to save some more space.
Title: Re: [REQUEST] Support for gzipped server.met
Post by: DLH on August 30, 2006, 07:13:01 PM
Quote
Originally posted by JusTiCe8
I resurrect this thread, as it could be a nice feature to don't waste disk space with all files which may grows too much like that:

347604 clients.met
7370984 clients.met.BAK
80280461 known2_64.met  (77 Mb !)
38463076 known2.met  (37 Mb !)

It should be not too hard to add transparent gzip compression in CFile class.

The *.met files are binary and you save nothing by compressing them, even with bz2; I would compare it to compressing mp3's. If you don't believe me try it yourself.
known2.met = 32801416
known2.met.bz2 = 32761787