Multiple DC++

megla · Post by **megla** » 2003-01-03 11:31

I know that DC++ can talk to many servers at the same time. But I would like to have more than one DC++ client at the same time. First some hubs don't alow more than one hub. And some hubs are very keen about whats in there share. So with multile DC++ clients with diffrents configurations you can solve connect to many at the same time without the OP's knowing and the shared folders will be right for all hubs.

Iceman[grrrr] · Post by **Iceman[grrrr]** » 2003-01-03 11:41

I never saw it this way, you could post it in the features tracker.

Maybe Arne will like it too!

https://sourceforge.net/tracker/?group_ ... tid=427635

ivulfusbar · Post by **ivulfusbar** » 2003-01-03 11:51

multiple dc++-clients will certainly make bandwidth, max slots, max hubs polices less effective for hubowners.

The problem could be solved with allowing different shares / hub. This would require lots of coding and GUI. Multiple file-lists, Multiple hashes etc so it would be memory-consuming. (only my thoughts)

if you run multiple dc++ make sure u use different "current directory" for them.

not-that-i-answered-your-question-but-you-got-to-hear-some-of-my-thoughts-ly'ers ;))

Iceman[grrrr] · Post by **Iceman[grrrr]** » 2003-01-03 11:53

yup it could be hell...

it would be preferable to have different share/hub and slots open only for certain hubs...

Jaw · Post by **Jaw** » 2003-01-03 12:05

Having Multiple DC++ clients active at the same time was/is possible using 0.18 & earlier!

megla · Post by **megla** » 2003-01-03 15:53

Any ideas why the removed that feature? Is nice that the default is i uses the already loaded version. But a parameter telling which instance would be nice.

Iceman[grrrr] · Post by **Iceman[grrrr]** » 2003-01-03 17:08

Maybe because conflicts could occur through the many open instanses.

ivulfusbar · Post by **ivulfusbar** » 2003-01-03 18:24

......and many hubadmins would not like it, it would set the hub/slots ratio out of play.

Trem0r · Post by **Trem0r** » 2003-01-04 07:12

As it is now with the dc++ tag as admins only hope of controlling their users this limit of one dc++ client has to be there. If everyone starts 2-3 clients then the dc++ tag will be obsolete and admins can't trust dc++ any longer. If clients without this limit gets popular my guess is that admins will ban dc++ users again and we really don't want that.

Nev · Post by **Nev** » 2003-01-05 08:32

I'd hate to see a dc++ that allowed for people having 20 dc++ open, all being on 3 hubs each with 9 slots open.

But dc++ could make each process communicate hubs and slots to eachother. That way, people could use several instances and H: S: would still be accurate.

Actually, this scheme would in a sense give us multiple windows, multiple shares and dedicated slots without much coding...

ivulfusbar · Post by **ivulfusbar** » 2003-01-05 08:38

do you mean that each instance whould have its own dc-port settings etc.. it gets more and more complicated... lots of threading sharing locking of files etc. It will take hellish amount of memory if we use the current lookup between what we call a file on dc and what its called on a harddrive....

this-gets-more-and-more-complicated-ly'ers ,))

Nev · Post by **Nev** » 2003-01-05 08:56

Hehe... remembering a Jack Handey from SNL:

"It's easy to sit there and say you'd like to have more money. And I guess thats what I like about it. It's easy. Just sitting there, rocking back and forth, wanting that money."

Hell-razor · Post by **Hell-razor** » 2003-01-05 19:13

the DC++ client type detection mod 0.181 has the ability to run several times.