Choosing between javascript and http communication. #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This changes the spec proposal so that a payment app can decide whether it wants to communicate with the user agent by means of HTTP or by means of javascript functions. The choice is implemented as an additional manifest field called communication_method.
|
Maybe the app should declare its supported protocols instead and let the mediator decide which is best for its platform/context. |
|
+1 to merging the PR (mostly to review it; not ready to endorse the proposal though yet). Thanks! Ian |
This lets the payment app declare which communication methods it supports so that the user agent can choose which method to use.
This sounds like a good idea. I pushed another commit that does this. |
|
Based on discussion in the TF we want to pick one way to do this and demonstrate that it is easy to acheive the other through a simple bridge (i.e. if we use HTTP then a JavaScript service worker can provide an offline JavaScript implementation and if we use JS then it can send messages to a remote service) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the spec proposal so that a payment app can decide whether
it wants to communicate with the user agent by means of HTTP or by means
of javascript functions.
The choice is implemented as an additional manifest field called
communication_method.
See issue #130