Click here to Skip to main content
16,014,591 members

Comments by sufi2008123 (Top 9 by date)

sufi2008123 17-Mar-11 5:47am View    
thanks to all

I Want

Once a thread is started,it shouldn't be blocking the UI and also wait to finish the thread.
sufi2008123 1-Mar-11 10:16am View    
thank u very very much for u r reply...


There are more than one IP in Address List and system (e.g computer) use one IP at a time, then can u give me the idea how to detect which is the primary IP (means which IP is Currently using).
sufi2008123 22-Feb-11 10:25am View    
contact me sufi2008@gmail.com
sufi2008123 12-Feb-11 1:22am View    
Thank u sir...
sufi2008123 11-Feb-11 0:56am View    
thank u sir.
You want to know why i need this. Please read the following line carefully specially point No. 3.I want to implement this, that why i need to use the same port.

Suppose that client A wishes to set up a TCP connection with client B and both are behind the NAT. We assume as usual that both A and B already have active TCP connections with a well-known rendezvous server S. The server records each registered client's public and private endpoints.

1. Client A uses its active TCP session with S to ask S for help connecting to B.
2.S replies to A with B's public and private TCP endpoints, and at the same time sends A's public and private endpoints to B.

3.From the same local TCP ports that A and B used to register with S, A and B each asynchronously make outgoing connection attempts to the other's public and private endpoints as reported by S, while simultaneously listening for incoming connections on their respective local TCP ports.

4.A and B wait for outgoing connection attempts to succeed, and/or for incoming connections to appear. If one of the outgoing connection attempts fails due to a network error such as “connection reset” or “host unreachable,” the host simply re-tries that connection attempt after a short delay (e.g., one second), up to an application-defind maximum timeout period.

5.When a TCP connection is made, the hosts authenticate each other to verify that they connected to the intended host. If authentication fails, the clients close that connection and continue waiting for others to succeed. The clients use the first successfully authenticated TCP stream resulting from this process.