PHP CURL w/o waiting for response

[Judahnator]

I am writing an API, and i need it to ping another server but not wait for a response.

 

The API I am writing must be as low-latency as possible, and the next server it sends a request to needs several seconds, sometimes even a full minute, to finish its task. This second script does not generate any output, so waiting for the servers response would only waste time.

 

How could i use CURL (or whatever) to do this? I have read that it is possible, however i cannot seem to find out how its done.

 

 

Thanks in advance!

[SSL]

What language are you using?

[Neil]

What language are you using?

Says in the topic: php

There's no good way to do this, as php is (by design) a blocking language. Which means it will wait for the function to finish before continuing.

Some suggestions include:

1. Lower the curl timeout opt to something very low.

2. Use a socket to generate the http request manually, and then close the socket after opening.

[SSL]

There's no good way to do this, as php is (by design) a blocking language. Which means it will wait for the function to finish before continuing.

 

PHP wasn't designed. That would imply that some thought was actually put into the language.

[keja]

Have you tried with exec + nohup ?

 

something like:

exec("nohup ping.php > /dev/null 2>&1 &");

 

its not super optimized and bit heavy on resources, but as said before php is a blocking language, so there is no perfect solution.

[Neil]

Have you tried with exec + nohup ?

 

something like:

exec("nohup ping.php > /dev/null 2>&1 &");

 

its not super optimized and bit heavy on resources, but as said before php is a blocking language, so there is no perfect solution.

 

Eww no. Never use exec. Or shell_exec. Or passthru. Or any of those functions. They're almost never necessary.

[Judahnator]

Says in the topic: php

There's no good way to do this, as php is (by design) a blocking language. Which means it will wait for the function to finish before continuing.

Some suggestions include:

1. Lower the curl timeout opt to something very low.

2. Use a socket to generate the http request manually, and then close the socket after opening.

 

Thanks for that, i ended up going the socket route.

[TheKnower]

On 5/25/2015 at 3:53 AM, Judahnator said:

 

Thanks for that, i ended up going the socket route.

Could you tell me how you did that I'm trying to do something similar