> On 24 Jan 2017, at 11:13 pm, Jake Archibald <notifications@github.com> wrote: > > @marcoscaceres > > There is no "Payment app", just like there is no "Geolocation app", and no "Push Notification App" - supporting "payment handling" is just another (permission gated) powerful feature - there is nothing special about these kinds of web applications. > > There's one "push notification" permission per origin, but there's up to one "push subscription" per service worker, meaning there can be many per origin. > I'm trying to say exactly what you just said. Language is hard :( > I've taken "payment app" to be akin to "push subscription". I agree that the permission part is per-origin. > That's also exactly how I'm viewing it. Why I don't like the whole "payments app" thing (and I think saying "app" is leading to problems and poor design choices) - it's a subscription of sorts... just another "powerful feature", as per Permission API parlance. > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. > -- 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/98#issuecomment-274811738
Received on Tuesday, 24 January 2017 14:09:40 UTC