Re: non-blocking request to a url (via curl or file_get_contents or whatever)...
| From: | Roman Neuhauser | Date: | Sat, 20 Jan 2007 20:26:50 +0000 |
| Subject: | Re: non-blocking request to a url (via curl or file_get_contents or whatever)... | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-247460@lists.php.net to get a copy of this message | ||
# jochem@iamjochem.com / 2007-01-20 16:50:48 +0100:
> Roman Neuhauser wrote:
> 1. user stuffs things into shopping basket on [my] site (data stored in session)
> 2. user goes to check out.
> 3. user chooses online payment.
> 4. user is redirected to online payment provider site
> 5. user completes payment successfully
> 6. online payment provider site contacts [my] site/server directly with transaction
> status/details
> 7. user is shown 'thank you' page on online payment provider site
> 8. user is redirected back to [my] site and shown 'real' 'thank you' page.
That was perfect, thanks a lot!
> normally in step 8 the webbug would be placed on the 'thank you' page,
> but in this case the data needed to craft the webbug's url is no
> longer available - the solution is to perform the request the the
> webbug's url represents directly from my server during the
> code that runs as a result of the request made by the online payment
> provider in step 6.
Is it important that the callback gets called synchronously? Is the
order reconstructible from the callback url? If not I'd write
a small script to fetch urls from a database table and feed them to
wget or similar.
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991