linuxdcpp-team team mailing list archive

[Big Muscle <689460@xxxxxxxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/689460

Title:
  Different share for different hubs

Status in DC++:
  Confirmed

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/689460/+subscriptions