a diffrent look - protocol problem

[coredlen]

why not just take an allready tested gpl code and use it. emule use the edonkey protocol with great success and it allows for :

1. hash signature
2. chuncks download
3. errors dealing & correction
4. multiple sources download

maybe a dc client can be build on this. take the file transfer system and use it. you can even consider using :

1. upload queue
2. secure identification for upload queue
3. chuncks upload for better spread of the file in the hub

[Twink]

well lets see, it would no longer be dc++ if it used the edonkey protocol. Basically a totally new project.

> 1. hash signature
Cologic is working on these, and they seem to be starting to work quite nicely, to test them out find the latest version of BCDC.

> 2. chuncks download
uh what is this?

> 3. errors dealing & correction
DC++'s new ZBlock compression safe transfers check the crc for each block/chunk (hmm maybe that means we have #2 then)

> 4. multiple sources download
They're coming, but I dont see them as a major neccessity, check the forums for previous posts on this.

> 1. upload queue
BCDC also has this, although it might work slightly differently then you wanted...

> 2. secure identification for upload queue
There are also topics on this.

> 3. chuncks upload for better spread of the file in the hub
Isn't this just multiple sources again?

Overall you really didn't suggest anything new, also you put a poll on ur post which is a "stupid newbie post" type thing to do.

[Sedulus]

and yes.. we do appreciate new ideas.. :)
please read some more and search some more next time though.. =)

..and no, I don't appreciate useless polls.. but this one is going so well that I'll just have to leave it in tact ;)

[GargoyleMT]

Perhaps using DC++ is a poor choice for you, you can try DC Mule.

Migrating the whole network to eDonkey is a poor choice. BlackClaw had a lot of useful comments about your post, but I'll wait for him to repost them.