Re: Strange SocketChannel.connect() behaviour
Hi Gordon, thanks for the quick reply!
Based on your information, I refreshed myself on the 3-way handshake. I
guess my problem is how this relates to the methods available in Java since
it is actually the C listen() method that handles the connections.
I guess I had been assuming that the Java open() was roughly equal to the C
socket(), the Java bind() was equal to the C bind(), and the Java accept()
was roughly equal to the combined C listen() and accept(). This would imply
that the Java accept() would need to be called before a client connect()
could complete. Since I'm getting the complete, the C listen() must be part
of the Java bind().
Without reading mounds of code, any idea how I could confirm this? Also,
does there exist an equivalent to the C listen() in Java or is this just
something out of a developers control?
Thanks again,
Dave
"Gordon Beaton" <n.o.t@for.email> wrote in message
news:444e5266$1@news.wineasy.se...
On Tue, 25 Apr 2006 11:52:02 -0400, DaveB wrote:
I currently have a client that is connecting to a server, however
the connect() is completing before the server even performs the
accept. Should the connect not be waiting for the server accept
before indicating it is complete?
The connection succeeds when the 3-way handshake is done, which
happens regardless of whether the server calls accept().
Try a simpler example:
public class MyClient {
public static void main(String[] args) throws Exception {
Socket s = new Socket("localhost", port);
System.out.println("connected");
}
}
public class MyServer {
public static void main(String[] args) throws Exception {
ServerSocket ss = new ServerSocket(port);
Thread.sleep(60000);
}
}
/gordon
--
[ do not email me copies of your followups ]
g o r d o n + n e w s @ b a l d e r 1 3 . s e