- From: adamroach <notifications@github.com>
- Date: Wed, 31 Aug 2016 15:27:07 -0700
- To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
Received on Wednesday, 31 August 2016 22:28:24 UTC
@adrianhopebailie -- still digging through some of the background material here, but I think the general approach here is pretty sound. In particular, I far prefer the use of a new event rather than message queues (in fact, I argued for a similar design in London). I'll note that going with actual service workers settles the issue of updating payment apps (we leverage the normal SW update mechanism), and makes it so we don't have to re-invent a registration concept for payment apps (in fact, that's one of the things I like most about this approach). As we discussed on the call today, I plan to revise the jsapi proposal to reflect this approach in time for our call next week. I _think_ I have enough information in this issue to do so. -- 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/issues/33#issuecomment-243921902
Received on Wednesday, 31 August 2016 22:28:24 UTC