Re: CLOSESOCKETFUNCTION not always called in multi
Luke Palmer via curl-library <[email protected]>
| Newsgroups | gmane.comp.web.curl.library |
|---|---|
| Message-ID | <CAOS2QfBoHFawm1eqm=LX5qG6p-+vVrCRxRAaGF9kFpsVcy9kCA@mail.gmail.com> |
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.html