Automatically adjust slots according to set hub:slot

ChunkyQ · Post by **ChunkyQ** » 2004-03-19 21:34

Many hubs have a required hub:slot ratio, often 1:1 or higher. When I go into more hubs that usual, I have to open more slots. This can get repetitive and annoying. I would like a Constant Hub:Slot setting. DC++ opens and closes slots when you connect or disconnect from a hub.

Qbert · Post by **Qbert** » 2004-03-19 22:12

I can't believe I was just thinking of how I might implement something very similar to this not more than two minutes before reading this post.

ChunkyQ wrote:I would like a Constant Hub:Slot setting.

ThatÃ¢â‚¬â„¢s what I was thinking of.

ChunkyQ wrote:DC++ opens and closes slots when you connect or disconnect from a hub.

But now youÃ¢â‚¬â„¢re confusing me. I was thinking of a preset amount of advertised slots for each hub you are in.

The problem I thought of is when there are people with the same nickname in separate hubs, since it would involve a bit of tricky work (which may not even be possible in all situations) to determine which hub they are in, and that work would probably not be instant and so youÃ¢â‚¬â„¢d leave the person connecting waiting. For this circumstance I say just pick one and pretend they are part of that hub. For everybody else, you should already know what hub they are in, and so then able to decrease the right advertised slots.

But then I rethought, thinking about the protocol. DoesnÃ¢â‚¬â„¢t the client receive information from the hub with connect strings for any connection thatÃ¢â‚¬â„¢s about to occur? If so, this information would already be associated with just a specific socket, but I then stepped back and realized at a much higher level its already associated with a single hub, the same hub that the other person is on.

Are there any mods which have features similar to either of our descriptions?

PseudonympH · Post by **PseudonympH** » 2004-03-20 09:44

Well, with BCDC++'s custom description format, you can hardcode a slot count to advertise in your tag, which is the only place most hubs check (from my experience anyway).

cyberal · Post by **cyberal** » 2004-03-20 16:44

since there is no protocol standard.. it will be hard to even get the min slot info... also.. for this feature to work.. dc would have to keep track of the slot ratio... and as a result of that also max slots... too much numbers to take into consideration for this to be good... what should DC++ do if the rules doesn't match? exit the hub?

Qbert · Post by **Qbert** » 2004-03-20 17:28

cyberal wrote:since there is no protocol standard.. it will be hard to even get the min slot info

Obviously this would only affect hubs that either identify or even require DC++.

cyberal wrote:dc would have to keep track of the slot ratio

The expected ratio would be constant. It would just always change the number of slots so that the ratio of hubs:slots equals the expected ratio, at least in ChunkyQ's suggestion.

cyberal wrote:and as a result of that also max slots

Are you speaking of my suggestion or CunkyQ's? Because for ChunkyQ's, it already keeps track of max slots, and that's what is always being changed when needed.

cyberal wrote:too much numbers to take into consideration for this to be good

I see only one new number needed for CunkyQ's suggestion, a defined ratio number. For my suggestion, information for ammount of slots would need be moved from the entire DC++ program, into information stored for each hub.

My suggestion would however be intentionally lying to the hub's in relation to what their share description tags should be, but then again I have still never found where its documented that hubs should always expect that this information is global for the entire DC++ program.

Code: Select all

S = number of slots you have open.

Post by **GargoyleMT** » 2004-03-22 19:24

Qbert wrote:The problem I thought of is when there are people with the same nickname in separate hubs, since it would involve a bit of tricky work (which may not even be possible in all situations) to determine which hub they are in

Hello, welcome to the issue that's makes the oft-requested per-hub shares nigh impossible.

Qbert wrote:Are you speaking of my suggestion or CunkyQ's? Because for ChunkyQ's, it already keeps track of max slots, and that's what is always being changed when needed.

No, Cyberal is referring to the fact that there are certain hubs that place a limitation on how many slots you can open up, at maximum. It's like maximum hub count, except different.

[ 660153 ] Automatic slot configuration Hubs based

cyberal · Post by **cyberal** » 2004-03-23 08:10

Qbert wrote:
cyberal wrote:since there is no protocol standard.. it will be hard to even get the min slot info
Obviously this would only affect hubs that either identify or even require DC++.

This would affect all hubs that care how many slots a user has

Qbert wrote:
cyberal wrote:dc would have to keep track of the slot ratio
The expected ratio would be constant. It would just always change the number of slots so that the ratio of hubs:slots equals the expected ratio, at least in ChunkyQ's suggestion.

The aspected ratio can never be a constant, since all hubs have different slots per hub rules. Let's say you have your constant to 2slots/hub and enter a hub that demands 3slots/hub... what to do then?

Qbert wrote:
cyberal wrote:and as a result of that also max slots
Are you speaking of my suggestion or CunkyQ's? Because for ChunkyQ's, it already keeps track of max slots, and that's what is always being changed when needed.

I'm speaking of the thread starters suggestion.. Your belongs in it's own thread. If that 3slots/hub hub had a max 10 slots rule... you can't enter more than 3 hubs or you will violate their rules.

Qbert wrote:
cyberal wrote:too much numbers to take into consideration for this to be good
I see only one new number needed for CunkyQ's suggestion, a defined ratio number. For my suggestion, information for ammount of slots would need be moved from the entire DC++ program, into information stored for each hub.

*number of hubs open, *number of slots open - *minslot, *maxslot, *slotratio & *maxhubs for each hub you are in. And all this must match.

Qbert · Post by **Qbert** » 2004-03-23 14:49

cyberal wrote:If that 3slots/hub hub had a max 10 slots rule... you can't enter more than 3 hubs or you will violate their rules.

Qbert wrote:My suggestion would however be intentionally lying to the hub's in relation to what their share description tags should be, but then again I have still never found where its documented that hubs should always expect that this information is global for the entire DC++ program.
Code: Select all
S = number of slots you have open.