It be useful to have a clear() method for interfaces that store things.

Hi @marcoscaceres,

With AdamR's guidance we added clear() methods for wallets and instruments along with other edits to align with your comments (which were mostly respect and xref fixes).

https://w3c.github.io/webpayments-payment-apps-api/#clear-method
https://w3c.github.io/webpayments-payment-apps-api/#clear-method-1

Ian

@marcoscaceres, does the current draft of the spec address your isssue?

Ian

Sort of, but not really (again, seems things were added in a rush to go to FPWD without wide review😢)...

Why do we have two interfaces with identical method signatures? We should just have a single AsyncDataStore interface for PaymentWallets and PaymentInstruments. That is:

    readonly attribute AsyncDataStore instruments;
    readonly attribute AsyncDataStore wallets;

We should really be talking to the IDB folks and aligning here on an interface.

What is currently there is not clear because there is no real transactional semantics for what happens if:

Promise.all([x.add("1"), x.clear(), x.add("2")]); 

As they all run in parallel without an associated task queue.

Great comments.

I found this link to the IDB editors' draft:
http://w3c.github.io/IndexedDB/

I'm happy to take an action to talk to them about alignment.

Ian

Would be good. We need a primitive that is an domain specific database, but with a common interface that looks a lot like an (async) map. We have also the Cache API for precedence here.