Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) from Anders Rundgren on 2016-05-20 (public-payments-wg@w3.org from May 2016)

From: Anders Rundgren <notifications@github.com>
Date: Fri, 20 May 2016 06:40:40 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc:
Message-ID: <w3c/webpayments/issues/130/220608293@github.com>

HTTP POST has unlike a (properly defined) JS interface numerous of disadvantages including the lack of a merchant security context and handle to the calling window.  It has one advantage though: The lack of a security context completely removes SOP issues from the equation :-)

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/130#issuecomment-220608293

Received on Friday, 20 May 2016 13:41:14 UTC