I just wanted to say that version 0.1.0 showed great improvement over the previous ones. First the compilation occur with no problems and a lot faster then before(no more common c++). giFT doesn't get segmentation faults anymore(even if halo-kazza actually does if I leave it alone for long). Also the downloads are much better. I managed to perform many of then successfully.
Anyways I have a couple of sugestions to make(just some ideas). For once you should have giFT running from within halo-kazaa. that way you don't have to run it from a terminal to just follow it's events.
Something to record the changes on Settings would be nice too. Another things is to provide more information on the search list. like bandwith, bitrate(for mp3s), and something like that.
Well these are just a few sugestions, but overall I'm happy to see how halo-kazaa is improving.
Luiz Paulo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is nice work and I did manage to get a few files to download.
I don't know if it is the server's fault or the clients, but I can't seem to resume files. I would consider that would be a MAJOR improvement since I wouldn't have to start over at 0 bytes.
The second major improvement would be if all files of at least similar name and size (it would be great if the server also sent a CRC value with the file list... that way you could use the size and CRC values to match like files without similar names. At the same time it could be used to tell if you're copy is complete.) were grouped together as one file with N available servers, which the client would fall back to if the file timed out, or otherwise failed. It would also be nice to select it to sort by either ping or #of hops to target (even more advanced, # of IP domains in hops to target and #of dns domains in hop to target.)
There is actually a short list of my first take on ideas for improvement in the features area...
However #1 would be the ability to queue downloads (Someone else suggested that it was possible but in 0.1.0 I see no such feature...)
#2 is a resume feature.
#3 is something to automatically try secondary servers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So far so good. New version 0.2.0, seems much more stable, has a cleaner UI (new entries don't follow default settings, but the custom ones, yay!), and has rudimentary file sorting, with multiple host downloading.
If I can figure out how to go light enough to not crash this I can finally start shutting down my download slave wintel box.
So #1 still untested...
#2 doesn't apear to allow resume yet.
#3 basic functionaly and MAJOR improvement.
Pretty good considering a turn around of less then two weeks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I just wanted to say that version 0.1.0 showed great improvement over the previous ones. First the compilation occur with no problems and a lot faster then before(no more common c++). giFT doesn't get segmentation faults anymore(even if halo-kazza actually does if I leave it alone for long). Also the downloads are much better. I managed to perform many of then successfully.
Anyways I have a couple of sugestions to make(just some ideas). For once you should have giFT running from within halo-kazaa. that way you don't have to run it from a terminal to just follow it's events.
Something to record the changes on Settings would be nice too. Another things is to provide more information on the search list. like bandwith, bitrate(for mp3s), and something like that.
Well these are just a few sugestions, but overall I'm happy to see how halo-kazaa is improving.
Luiz Paulo
It is nice work and I did manage to get a few files to download.
I don't know if it is the server's fault or the clients, but I can't seem to resume files. I would consider that would be a MAJOR improvement since I wouldn't have to start over at 0 bytes.
The second major improvement would be if all files of at least similar name and size (it would be great if the server also sent a CRC value with the file list... that way you could use the size and CRC values to match like files without similar names. At the same time it could be used to tell if you're copy is complete.) were grouped together as one file with N available servers, which the client would fall back to if the file timed out, or otherwise failed. It would also be nice to select it to sort by either ping or #of hops to target (even more advanced, # of IP domains in hops to target and #of dns domains in hop to target.)
There is actually a short list of my first take on ideas for improvement in the features area...
However #1 would be the ability to queue downloads (Someone else suggested that it was possible but in 0.1.0 I see no such feature...)
#2 is a resume feature.
#3 is something to automatically try secondary servers.
So far so good. New version 0.2.0, seems much more stable, has a cleaner UI (new entries don't follow default settings, but the custom ones, yay!), and has rudimentary file sorting, with multiple host downloading.
If I can figure out how to go light enough to not crash this I can finally start shutting down my download slave wintel box.
So #1 still untested...
#2 doesn't apear to allow resume yet.
#3 basic functionaly and MAJOR improvement.
Pretty good considering a turn around of less then two weeks.