Shulou(Shulou.com)06/01 Report--

The main content of this article is to explain "asynchronous request PHP server, do not return data how to do", interested friends might as well take a look. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "asynchronously request PHP server, what to do if the data is not returned?"

Recently, a problem with ajax asynchronous requests has been discovered. When you request a PHP server with $.post, $.get, and $.ajax, you will never be able to return data asynchronously.

After many tests, it was found that:

-different browsers, request different domain names.-No blocking: no experiment required.

-different browsers, request with the same domain name-No blocking: session_id () returns different

-same browser, request different domain names-No blocking: session_id returns different

-same browser, same request and same domain name-blocking: session_id () returns the same

Discover the problem:

1 close XDEBUG

2 SESSION lock

3 clear output buffer

1 close XDEBUG

XDEBUG is real-time debugging. When debugging, it maintains the FPM to ensure that the thread is working to avoid data contamination.

Typically, when debugging with XDEBUG, open another browser and visit the site, which is inaccessible at this time.

This has a significant impact on parallel responses, that is, even if the front end sends multiple requests, it is controlled by XDEBUG and can only respond to one at the same time.

In addition, because XDEBUG depends on SESSION, turn off the session lock even if you use session_write_close () (see below). XDEBUG will still open automatically.

2 SESSION lock

Close the write lock on SESSION with session_write_close (), which is suitable for cases where SESSION is saved as File. If SESSION is saved in Redis, it is not required.

3 clear output buffer

Using session_write_close () may not close the SESSION lock immediately, so add: ob_end_flush () before this method. Let session_write_close () take effect immediately.

4 exampl

In the following example, when you click the "submit" button, the frontend sends two requests to the backend server.

One is a get request, which is requested every 1 second.

One is the post request, which is sent at the beginning and then waits for the corresponding end.

Look at the HTML code.

$('form') .on (' submit', function (e) {e.preventDefault (); / / request the server var id = setInterval (function () {$.get ('save.php?action=get', {}, function (data) {console.log (data) every other second) }, 'json');}, 1000); $.post (' save.php?action=post', {}, function (data) {console.log (data); / / stop timing cycle clearInterval (id) }, 'json');})

Php code

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.