On Wed, 30 May 2001, Rodney Myers <[EMAIL PROTECTED]> wrote,
> Date: Wed, 30 May 2001 12:46:06 +0100
> From: Rodney Myers <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: Silent Ending
>
> Hi,
>
> Thanks for your commnets, and yes this is a rare situation.
> I develop a shopping system, in client side javascript.
> I am interfacing to a payment system on a secure server.
> I need to send the Payment Service Provider various data including several
> URLs.
> To one of these URLs they will be POSTing back data which is intended for
> the merchant and not for the shopper. (The shopper already has what they
> need on the browser screen).
>
> In client side javascript I cannot receive POST data.
> Our client/merchants do not usually have their own servers and may not have
> cgi-bin privileges with the server space they rent. So I wish to provide a
> mechanism for them to receive this POST data.
>
> So for the URL I am sending a perl script in our own domain. I am also
> sending the merchants URL and some other data in a query string that will be
> returned untouched when the URL is called.
>
> I then take data from the query string including the merchants email address
> AND the POST data and compose an email to the merchant address.
>
> Meanwhile the shopper is getting various screens from the secure server, and
> an email of the original order, so the shopper is taken care of.
Sounds like you need a background process that doesn't need
to respond to the browser directly. So you cannot put the
process at the end.
No mattern how complicate the process, how many times URLs
are sent back and forth, at the end, you still need to say
something to the browser. And you really have to know the
cycle of your process.
s.a.n
--
Hasanuddin Tamir: [EMAIL PROTECTED] - Trabas: www.trabas.com
