Re: [w3ctag/design-reviews] Web Audio API: RenderCapacity API (Issue #843)

Sorry for the long delay. We've discussed this during our F2F, and having some level of consistency/interoperability between this proposal and compute pressure would be a better architectural direction. (Setting aside QoS and how to make that proposal consistent, as it seems much earlier stages)

Some questions for you:

1. Can you consider to have a common interface for pressure signal shared between Compute Pressure and RenderCapacity? If not, why?
2. Can you consider using an Observer for your use case? If not, why? (We will ask the opposite about Compute Pressure and events)
3. Where does the working group stand with respect to limiting the granularity of the pressure?  Do you have agreement about limiting granularity in the absence of some gating function, like gaining permission for microphone or similar?

With all of these questions, we think the use cases are valid so no questions there.

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

Message ID: <w3ctag/design-reviews/issues/843/1905877868@github.com>