Re: how do I reunite 2 separate requests

It is similar except that its all pages returned to the user are from our site. Thanks for the response - I think its starting to unscrabble in my head now :-) On 12/28/06, Will Tomlinson <[EMAIL PROTECTED]> wrote: > > This kinda sounds like Paypal Integration. They have PDT and IPN. > Before the

Re: how do I reunite 2 separate requests

on(txn); > > Use info from txn.getResponse() > > > -Original Message- > From: Michael Traher [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 28, 2006 11:30 AM > To: CF-Talk > Subject: Re: how do I reunite 2 separate requests > > Thanks Russ, > >

Re: how do I reunite 2 separate requests

thats OK, because the call and response are on the server - cfhttp and process cfhttp.filecontent, so if the users browser crashes - it just means they won't know what happened - but the system does. On 12/28/06, Snake <[EMAIL PROTECTED]> wrote: > > Well there is a potential problem with that meth

Re: how do I reunite 2 separate requests

This kinda sounds like Paypal Integration. They have PDT and IPN. Before the user moves to paypal's site, I log the order as unfinished/not approved, etc. I send the cfid and token in the url to paypal. The user does their thing at paypal, bounces back to my site with cfid/token in url, I disp

RE: how do I reunite 2 separate requests

PROTECTED] Sent: Thursday, December 28, 2006 11:30 AM To: CF-Talk Subject: Re: how do I reunite 2 separate requests Thanks Russ, Yes I guess getting the callback page to write to the database, and then the original request read and wait for that database value is a way to solve this. And yes we

RE: how do I reunite 2 separate requests

-Original Message- From: Michael Traher [mailto:[EMAIL PROTECTED] Sent: 28 December 2006 16:30 To: CF-Talk Subject: Re: how do I reunite 2 separate requests Thanks Russ, Yes I guess getting the callback page to write to the database, and then the original request read and wait for that database

Re: how do I reunite 2 separate requests

Thanks Russ, Yes I guess getting the callback page to write to the database, and then the original request read and wait for that database value is a way to solve this. And yes we do pass a unique transaction reference to identify the value - its just a bit clunky compared to it all being in one r

RE: how do I reunite 2 separate requests

This is a pretty standard callback method, most systems will use it. When you sent the request, you should have the option of sending a custom value, such as your own generated transaction or invoiceID. If not then you could always send the CFID and CFTOKEN. This is what you need to use on the call