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

[emacsq]

> But it's not just letting connections linger, url-http has a
> mechanism to store open connections in a hash and reusing them:
>
> Does someone here know what the point of this was?

It looks like it's not for later requests to use this stored
connection, but if during the same request a connection is
used in various functions then the connection object is not
always available there. So the author stored the connections
in a hash table, so he can retrieve them from anywhere, it's
a common shared storage for connections.

This is all right. The problem is when the url-retrieve ends then
the connection is left in the hastahble open which is OK for
platforms like Linux with plenty of sockets, because later
they are cleaned up  anyway.

But in case of windows with the 32 process limitation it's
clearly a bug, because the lingering pocesses use up the
available sockets, so while the limit is there, these
processes should be closed when the callback is called.

This is a quick and simple fix which solves the problem
until the limiting code is reenginered by someone  sometime
in the future, and even then this fix can stay, because there
is no point in leaving unsued open connections laying around.