Article View: borland.public.cppbuilder.internet.socket
Article #4217Re: detect router
From: Jonathan Benedicto
Date: Tue, 22 Mar 2005 00:13
Date: Tue, 22 Mar 2005 00:13
38 lines
2687 bytes
2687 bytes
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message news:423b4b3b$1@newsgroups.borland.com... > But then, how does the user who has the file know where to send it > to? > Simple - both parties have to be connected to the same public > server, who > then keeps track of the Internet IPs of every user so it can tell > each party > where the other party is located. That is exactly how Kazaa, and > also IM > services (ICQ, AIM, etc) work - everyone is connected to the main > database > server, who then knows where everyone is. When one user wants to > establish > a connection with another user, the main server has to act as an > intermediary while both parties negotiate to decide whom will > connect to > who. If one user cannot connect to another, then they try reversing > the > direction of the connection and try again. A router may not be able > to > route incoming connections from the outside world to a private > machine, but > a private machine can always make an outgoing connection to the > outside > world. Once the connection is established, it doesn't matter who > sends > commands and who processes them. Sockets are bidirectional. The > user who > is arunning the server socket for the connection can still be the > one to > send commands to the user who is running the client socket for the > connection. How does the other client know that someone is trying to connect to it to retrieve a file ?
Technical Details
Message-ID:
<423f632d@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<423a7852$1@newsgroups.borland.com> <423a95b5$1@newsgroups.borland.com> <423aa0ca$1@newsgroups.borland.com> <423ab09b@newsgroups.borland.com> <423ac0ff@newsgroups.borland.com> <423ada46$1@newsgroups.borland.com> <423b0983@newsgroups.borland.com> <423b1ceb$1@newsgroups.borland.com> <423b3d0f$1@newsgroups.borland.com> <423b4b3b$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,a79eaa4c33b47254 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Jonathan Benedicto" <incorrect@no.server> Newsgroups: borland.public.cppbuilder.internet.socket References: <423a7852$1@newsgroups.borland.com> <423a95b5$1@newsgroups.borland.com> <423aa0ca$1@newsgroups.borland.com> <423ab09b@newsgroups.borland.com> <423ac0ff@newsgroups.borland.com> <423ada46$1@newsgroups.borland.com> <423b0983@newsgroups.borland.com> <423b1ceb$1@newsgroups.borland.com> <423b3d0f$1@newsgroups.borland.com> <423b4b3b$1@newsgroups.borland.com> Subject: Re: detect router Date: Mon, 21 Mar 2005 19:13:33 -0500 Lines: 40 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-RFC2646: Format=Flowed; Original NNTP-Posting-Host: 69.158.101.206 Message-ID: <423f632d@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1111450413 69.158.101.206 (21 Mar 2005 16:13:33 -0800) Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail