curl-library
Choosing between CURL multi vs easy interface
Date: Sun, 5 Jul 2015 22:18:04 +0100
Hello,
I have a server application where each worker thread must make a GET to the
same third-party HTTP server.
Currently, this is implemented by having a CURL easy handle per worker
thread in the application.
As it stands, when the third-party HTTP server is behaving erratically, my
applications faces issues like timeouts and errors in resolving host name,
that causes a backlog of requests to my server that cannot be handled in a
timely manner.
Any advice on the following would be greatly helpful -
- Would CURL multi interface allow my application to serve more
concurrent requests? Is it better than the easy interface in this scenario?
- From intermittent errors related to host name resolution, it appears
that a DNS lookup is being done frequently for the same third-party HTTP
server. Is there a way to cache the DNS lookup?
Thanks in advance,
Raj
-- This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of BlisMedia Ltd, a company registered in England and Wales with registered number 06455773. Its registered office is 3rd Floor, 101 New Cavendish St, London, W1W 6XH, United Kingdom. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-07-05