Sort of an aside note: You have two variables at work here, requests and responses. There's also the fact that you can't "really" do anything simultaneously (thanks to the event loop, you can only do one thing at a time).
Also, while you can send a request at (nearly) the same time, you're not allowed to expect a response back from the server to be analogous to the req. Think about if your server takes a shit for the second request and times out, you'll never get a response. If you really need the 2-requests, and the 2-responses to go out and come in at the same time/ you'll need to refractor and send only one request. Otherwise you will have to cache the first response (in order of response time, not request order) through some sort of global handler that looks to see if it's handling the first or second request. If it's the first response, the global handler will need to cache the response and wait foe the second to come in, when you can handle both truly at the same time. Jsfiddle to come Chase Wilson On the iPhone On Aug 8, 2011, at 1:27 PM, Sid-ahmed D <[email protected]> wrote: > Okay, > i need close Session after get all SESSION datas. > > session_start(); > $datas = $_SESSION; > session_write_close(); > > > On Aug 8, 10:17 pm, Sid-ahmed D <[email protected]> wrote: >> Thank you ! you are genious ^^ >> commom object is session_start (). >> >> When i remove this ... >> GET test.php 200 OK 5.03s >> GET test2.php 200 OK 5.03s >> >> BUT ... i need to my session ... >> >> On Aug 8, 10:07 pm, Sanford Whiteman <[email protected]> >> wrote: >> >> >> >> >> >> >> >>>> The requests on the back end, check if i receive a new message (mail) >>>> and on the front end users can refresh or change page with other >>>> Request.HTML. >> >>> What else is in common between the two requests? Think session >>> variables, cache locks, etc. You have to narrow this down. For >>> starters, just set up two dummy back end pages (no database code, >>> session or other dependencies) and I'm sure you'll see they are truly >>> independent. Then debug from there. >> >>> -- S.
