- From: Shane McCarron <notifications@github.com>
- Date: Sun, 07 Aug 2016 12:49:56 -0700
- To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
Received on Sunday, 7 August 2016 20:02:02 UTC
> <h3>Network Considerations</h3> > <ul> > <li>This specification only describes communication between the user agent and the payment app. This includes an > asynchronous mechanism for a payment app to return a payment response to the user agent. This specification > - does not address scenarios where the user agent does not receive the response (e.g., due to a crash our > - network outage).</li> > + does not (yet) address scenarios where the user agent does not receive the response (e.g., due to a crash our > + network outage). Question: Should we recommend asynchronous communication between payment app and servers it talks to?</li> Instead of embedding this question, I suggest you raise an issue and then put an issue marker in the spec. --- 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-payment-apps-api/pull/19/files/f17221097d5b71d07091af0d6665c6d924616ba8#r73807968
Received on Sunday, 7 August 2016 20:02:02 UTC