Re: [w3ctag/design-reviews] Budget API (especially reserve() method) (#169)

Hey @owencm: thanks for the reply and for marking the TODOs. Also, thanks for the notes on the format. We note that you requested that we provide feedback as issues on your repo and we'll break out the notes thus far as separate issues. We provided some quick feedback here due to timeliness concerns; apologies for the difficulty.

We took this up today at the F2F meeting in TOK. Notes below are from the group discussion with @torgo, @triblondon, and @ylafon.

 * Regarding the Explainer, thanks for noting that the `README` is the place to look. Looking forward to seeing it expanded.
 * @torgo mentions that the Security and Privacy considerations section might want to include notes about what this API behaves when in private browsing mode. Specifically, advice for authors of specs that will integrate with Budgets
 * What operations would be modeled as budget-able but wouldn't also be introspectable via the Permissions API? As registries are an open problem for web specs, we'll ping back when we come up with a solution.
 * @triblondon notes that the model the API presents weights all silent pushes (e.g.) to be equal. Do we have confidence that this will always be true? Has a model been considered in which the developer requests some budget for an operation and is then limited to that budget (e.g., execution time)?

We'll convert the above into issues on your repo today.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/169#issuecomment-298148277