Ideas to identify a user within userconnection
Moderator: Moderators
Ideas to identify a user within userconnection
If u are in like 3 hubs and there exists 3 years with the same nick, one in each of these hubs. And u send ConnectToMe to one of them. How in earth would u make it possible to tell him aport from the others once he connects to your client? I mean there is no real way build in to dc++ to know which hub/user this connection originates from. Anyone have ideas to make it more reliable?
You can always reach me nowhere!
you could use one listening port per hub..
I think QuickDC does that.. I've heard Offset talk about it at least
I think QuickDC does that.. I've heard Offset talk about it at least
http://dc.selwerd.nl/hublist.xml.bz2
http://www.b.ali.btinternet.co.uk/DCPlusPlus/index.html (TheParanoidOne's DC++ Guide)
http://www.dslreports.com/faq/dc (BSOD2600's Direct Connect FAQ)
http://www.b.ali.btinternet.co.uk/DCPlusPlus/index.html (TheParanoidOne's DC++ Guide)
http://www.dslreports.com/faq/dc (BSOD2600's Direct Connect FAQ)
the incoming connection sends his/her nick first,
User::Ptr& ClientManager::getUser(thatNick) is consulted
that User has a specific hub, hence we know our name
(this will give conflicts when two nicks are the same in different hubs, yes)
User::Ptr& ClientManager::getUser(thatNick) is consulted
that User has a specific hub, hence we know our name
(this will give conflicts when two nicks are the same in different hubs, yes)
http://dc.selwerd.nl/hublist.xml.bz2
http://www.b.ali.btinternet.co.uk/DCPlusPlus/index.html (TheParanoidOne's DC++ Guide)
http://www.dslreports.com/faq/dc (BSOD2600's Direct Connect FAQ)
http://www.b.ali.btinternet.co.uk/DCPlusPlus/index.html (TheParanoidOne's DC++ Guide)
http://www.dslreports.com/faq/dc (BSOD2600's Direct Connect FAQ)
and the solution is ofcourse to include hubname/hubaddy in the connection attempt.. how this can be done however, i leave to you
http://whyrar.omfg.se - Guide to RAR and DC behaviour!
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet
Possible solution:
A and B are clients, A sends a $ConnectToMe to B. B receives this through hub X and starts the connection.
Add an item to the $Supports list called "HubID". If both clients support this then client B sends a command sometime in the handshake of the following form:
So now both clients know which hub the connection was made through.
A and B are clients, A sends a $ConnectToMe to B. B receives this through hub X and starts the connection.
Add an item to the $Supports list called "HubID". If both clients support this then client B sends a command sometime in the handshake of the following form:
Code: Select all
$HubID <Hub IP>:<Hub Port>|
yes exactly, this can't be very hard to do. Make this happen and the biggest problem is solved.. GREAT!
http://whyrar.omfg.se - Guide to RAR and DC behaviour!
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet
-
- Posts: 506
- Joined: 2003-01-03 07:33
no, $HubId with hubip and hubport can not be used, many hubs are multihomed. Mine and xayides "home" hub for example. And more and more hubs supports more than one port to make sure that users with ivul isps can still connect.
We have discussed this before, and i think if this is needed, a extension to the protocol must be made, and then you get into extension of the protocol. Either in the connections-commands in the hub-client protocol or in a pure CTCP-devolopment solution (ooh.. i wonder how many times i have talked about CTCP here.. ;)) )
it-can-be-solved-in-so-many-ways-but-most-of-them-cost-alot-ly'ers.
We have discussed this before, and i think if this is needed, a extension to the protocol must be made, and then you get into extension of the protocol. Either in the connections-commands in the hub-client protocol or in a pure CTCP-devolopment solution (ooh.. i wonder how many times i have talked about CTCP here.. ;)) )
it-can-be-solved-in-so-many-ways-but-most-of-them-cost-alot-ly'ers.
Everyone is supposed to download from the hubs, - I don´t know why, but I never do anymore.
but there must be a way to solve the situation where two users that will connect to eachother are connected to the same hub via different ports, in such a situation.. can't the app just ignore the hub port and match it to the addy alone? Ah well, ofcourse.. that same user could potentially be connected to a different hub on the same ip.. not very likely though..
http://whyrar.omfg.se - Guide to RAR and DC behaviour!
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet