W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)

From: Jason Normore <notifications@github.com>
Date: Thu, 19 May 2016 08:24:30 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/130/220359266@github.com>
What's the advantage of requiring a ``getRequest`` call over just including it in the POST params in either case? The POST request to ``start_url`` happens in both cases, even if it's a static page with some javascript (mentioned above as a valid performance concern for some merchants) the payment app can handle the params in the client-side javascript rather than introducing a new way to communicate.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Thursday, 19 May 2016 15:25:27 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 May 2016 15:25:28 UTC