Different share for different hubs

[Szabolcs Molnár]

A long-awaited feature is that the user should be able to define different shares for different (adc) hubs. This should be implemented.

I can imagine several ways to do it:

1) Define share on per-hub in favorites. This seems to be a not-too-good idea.
2) Since now we have "hub groups", we could invent "group share" which would let the user to define custom share for a group. In this case we should disable the "customize share for this group" switch if there are NMDC hubs in the group and we should disable the possibility to move an NMDC hub to a group with a customized share (this would eliminate future bug reports).
3) Moving from 2) a little bit further, the "group property page" could contain some other settings too which could be customized per-group favor, like a "profile" page with default nick for a group, etc.

[Szabolcs Molnár (fleet)]

Posting two mockups how I think a group settings dialog could look like. Obviously it's not ready, for example, we should state somewhere on a visible place that some settings are only applied for ADC hubs. Also, on the General page, we could put some custom identity too in the (now empty) second group.

[Night (night.)]

I wont comment on how to do shares part, but the problems one might have to get it working correctly.

Ok, lets imagine we are at 2 adc hubs with a same user, different shares in each hubs.
user takes the list from hub1, he gets it just fine and its a correct one, BUT here comes the problem:
he then takes list from hub2, he will get the same list as before (from hub1),
it will use the same userconnection that started from hub1, because the user is considered to be the same if he has the same CID.

So either the client should have Hub spesific userconnections, or the connection reguest should be bind to a hub somehow.
One solution might be to send mySID in the GET reguest when reguesting a filelist from users,
so uploader could then update connection to right hub.
CGET list / 0 -1 ID*mySID*

for responding to File upload reguests we could just use CID to find all the same hubs with the user and then decide to give it or not,
he could get them anyway if they are shared even in one of the hubs.

[Big Muscle (bigmuscle)]

I think that your remark is connected with the bug #206778.

I think that
a) hub-specific userconnections
b) disconnect userconnection and make a new one when connection in different hub is wanted
should be the only correct solutions.

Adding any hub/sid/etc. information into GET command would increase a risk that users will be able to ask for files from different hubs and I don't think it is correct. The feature should be done transparently, i.e. downloading client should not know about the fact that remote user can have different shares in two hubs.

[iceman50 (bdcdevel)]

Just adding a diff of some of the work Night did on DiCe for separate shares per hub along with additional fixes for picking a hub a search came from http://pastebin.com/TyA5zaW6

[iceman50 (bdcdevel)]

I was just given a new diff by night apparently there were some things missing from the previous one .. <http://files.airdcpp.net/dice.diff>

[Fredrik Ullner (ullner)]

The patch from the above comment, reposted so as to not lose it if the AirDC++ site is unavailable.