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

The WebRTC IdP registration isn't persistent -- it's added to each RTCPeerConection object after it's created. So it's not exactly the model to look at. When I mentioned it as a potential model for the local portion of payment apps, I meant it more as a model for the communication channels.

All of that said, with the discussion of POST as a desired means for communication with payment apps, I think we might want to reconsider how this all works. I'm not terribly happy with having multiple ways to accomplish the same thing, since it makes implementation and testing of the system that many times harder.

So, if we're going down the POST path, I would suggest we contemplate using POST for all interactions, and describe how to use service workers to process such requests locally.

Note that this doesn't change how websites interact with the whole payment system at all -- these POSTs are generated by the mediator rather than by the web page anyway.

---
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-220180799