Message116854
when use multiprocessing managers, while use socket to communicate between server process and client process, if I used the global socket timeout feature(no matter how large the value is) the client will always say
File "c:\python27\lib\multiprocessing\connection.py", line 149, in Client
answer_challenge(c, authkey)
File "c:\python27\lib\multiprocessing\connection.py", line 383, in answer_challenge
message = connection.recv_bytes(256) # reject large message
IOError: [Errno 10035]
this is not reasonable, because this behaviour will make subprocess unable to use socket's timeout features globally.
Another question is line 138 in managers.py:
# do authentication later
self.listener = Listener(address=address, backlog=5)
self.address = self.listener.address
backlog=5 will accept only 5 cocurrent connections, this is not so user friendly, you'd better make this a argument that can be specified by user |
|
Date |
User |
Action |
Args |
2010-09-19 10:06:31 | hume | set | recipients:
+ hume |
2010-09-19 10:06:31 | hume | set | messageid: <1284890791.64.0.603170640253.issue9897@psf.upfronthosting.co.za> |
2010-09-19 10:06:29 | hume | link | issue9897 messages |
2010-09-19 10:06:28 | hume | create | |
|