Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: CLOSESOCKETFUNCTION not always called in multi
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Luke Palmer via curl-library <curl-library_at_lists.haxx.se>
Date: Mon, 17 Feb 2025 14:54:14 -0500
Hi all,
I have exactly the same problem as Malcolm Matalka: I'm using libcurl with
an event framework that insists on being responsible for closing an FD that
it was previously told to watch. CLOSESOCKETFUNCTION doesn't always
apply to watched FDs at present because not every watched FD is a socket.
I have found that if I build with '--disable-socketpair' that I no longer
have problems with this. I wanted to both share this as a potential
solution and also to ask two questions:
Does this seem like a reasonable workaround? Might there be other potential
pitfalls?
What might the downsides be to using '--disable-socketpair'? I can't find
much information about why internal socketpair communication is good to
have.
Apologies for not threading: I just subscribed. Thanks all!
Luke
Date: Mon, 17 Feb 2025 14:54:14 -0500
Hi all,
I have exactly the same problem as Malcolm Matalka: I'm using libcurl with
an event framework that insists on being responsible for closing an FD that
it was previously told to watch. CLOSESOCKETFUNCTION doesn't always
apply to watched FDs at present because not every watched FD is a socket.
I have found that if I build with '--disable-socketpair' that I no longer
have problems with this. I wanted to both share this as a potential
solution and also to ask two questions:
Does this seem like a reasonable workaround? Might there be other potential
pitfalls?
What might the downsides be to using '--disable-socketpair'? I can't find
much information about why internal socketpair communication is good to
have.
Apologies for not threading: I just subscribed. Thanks all!
Luke
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2025-02-17