[Python-Dev] [Python-checkins] r42185 - python/trunk/Lib/test/test_socket_ssl.py (original) (raw)
Neal Norwitz nnorwitz at gmail.com
Thu Jan 26 02:54:05 CET 2006
- Previous message: [Python-Dev] [Python-checkins] r42185 - python/trunk/Lib/test/test_socket_ssl.py
- Next message: [Python-Dev] [Python-checkins] r42185 - python/trunk/Lib/test/test_socket_ssl.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1/25/06, Tim Peters <tim.peters at gmail.com> wrote:
Because the server doesn't set listenerready 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
- Previous message: [Python-Dev] [Python-checkins] r42185 - python/trunk/Lib/test/test_socket_ssl.py
- Next message: [Python-Dev] [Python-checkins] r42185 - python/trunk/Lib/test/test_socket_ssl.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]