Re: [Boost-users] boost::asio::tcp -> asyncconnect generates multiple sockets

Subject: Re: [Boost-users] boost::asio::tcp -> asyncconnect generates multiple sockets
From: Hert (gert_corthout_at_[hidden])
Date: 2011-07-08 04:40:26

Yes I understand that. This is not the issue. I am not considering the socket
generated by the acceptor (sorry for the confusion). The client side seems
to generate 2 sockets!

>From tcpview (sysinternals):
Test.exe:3440	TCP	PC-ENG1-13:3144	localhost:3145	ESTABLISHED	
Test.exe:3440	TCP	PC-ENG1-13:3145	localhost:3144	ESTABLISHED	
Test.exe:3440	TCP	PC-ENG1-13:3146	localhost:50000	ESTABLISHED	

The last one is the socket between the client and the server.
The first two connect to each other, but why are these generated?? We see
this happening after internally in the boost library the "reactor" is
started.
The demo program "chatserver" and "chatclient" have the same behaviour.

--
View this message in context: http://boost.2283326.n4.nabble.com/boost-asio-tcp-asyncconnect-generates-multiple-sockets-tp3647856p3653514.html
Sent from the Boost - Users mailing list archive at Nabble.com.