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.
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.