> On Feb 17, 2021, at 12:25 AM, Karen Shaeffer via Python-list
> wrote:
>
>
>
>> On Feb 16, 2021, at 8:10 PM, Jason Friedman wrote:
>>
>>>
>>> I set listen(2) and expect to see "error" when more clients than "the
>>> maximum number of queued connections" trying to connect the server. But,
> On Feb 16, 2021, at 8:10 PM, Jason Friedman wrote:
>
>>
>> I set listen(2) and expect to see "error" when more clients than "the
>> maximum number of queued connections" trying to connect the server. But, no
>> error!! Even 4 clients can run normally without problem.
>>
>> Am I misunderstan
Kushal Kumaran 在 2021年2月17日 星期三下午12:11:04 [UTC+8] 的信中寫道：
> On Tue, Feb 16 2021 at 07:24:30 PM, Jach Feng wrote:
> > I am experimenting with multithreading-socket these days. I build a
> > server to handle each client in a separate thread. All are running on
> > my local PC. It works fine except
On Tue, Feb 16 2021 at 07:24:30 PM, Jach Feng wrote:
> I am experimenting with multithreading-socket these days. I build a
> server to handle each client in a separate thread. All are running on
> my local PC. It works fine except the listen() method.
>
> I set listen(2) and expect to see "error"
>
> I set listen(2) and expect to see "error" when more clients than "the
> maximum number of queued connections" trying to connect the server. But, no
> error!! Even 4 clients can run normally without problem.
>
> Am I misunderstanding the meaning of this argument?
>
https://docs.python.org/3/lib
I am experimenting with multithreading-socket these days. I build a server to
handle each client in a separate thread. All are running on my local PC. It
works fine except the listen() method.
I set listen(2) and expect to see "error" when more clients than "the maximum
number of queued connect
