Re: What does the error "Process <URL> not running" mean?

[Robert Pluim <rpluim@gmail.com>]

>>>>> On Wed, 09 Feb 2022 16:17:32 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Robert Pluim <rpluim@gmail.com>
    Eli> Why do you think the Gnulib module is free from the same (or similar)
    Eli> limitation?  Isn't FD_SETSIZE = 64 in winsock2.h?
    >> 
    >> It is, but youʼre allowed to set it higher, as far as I know.

    Eli> Not with the Gnulib emulation, AFAICT, since they call the same API we
    Eli> call in Emacs, which is limited to waiting on 64 handles.

Youʼre right, Iʼd missed that. Thatʼs fixable, but then we still run
into the issue with supporting old Windows versions.

    >> Maybe it would be enough to just call winsock `select' from Emacs'
    >> select emulation, but only for sockets.

    Eli> That's ugly, complicated (sockets are handles, file descriptors
    Eli> aren't), and in some use cases will still hit the limit.

    Eli> These half-measures aren't the kind of a solution I'd consider as good
    Eli> candidates for replacing the current code.  We should probably use
    Eli> WSAAsyncSelect for sockets, and/or use several threads, each one
    Eli> watching 64 handles, to wait on 64*N handles.  _That_ would be worth
    Eli> it.

Yes, that does sound better, although given the unexpected
side-effects of my experiments with WSAEventSelect, it might be tricky
to get right.

Robert
--