A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-January/060083.html below:

[Python-Dev] [Python-checkins] r42185 - python/trunk/Lib/test/test_socket_ssl.py

[Python-Dev] [Python-checkins] r42185 - python/trunk/Lib/test/test_socket_ssl.py [Python-Dev] [Python-checkins] r42185 - python/trunk/Lib/test/test_socket_ssl.pyNeal Norwitz nnorwitz at gmail.com
Thu Jan 26 02:54:05 CET 2006
On 1/25/06, Tim Peters <tim.peters at gmail.com> wrote:
>
> Because the server doesn't set listener_ready until after the server
> has done listen(),  and the client waits for that event, it "should
> be" 100% reliable that the client's connect() succeeds.
>
> Or do you have some other race in mind?

That's what I was thinking of.  I thought you had to be accept()ing
prior to connect() working.  I thought listen() only sets the # of
outstanding connections allowed (basically internal buffer).  But if
the listen() is sufficient, I agree there is no race.

n
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4