- From: Shunya Shishido <notifications@github.com>
- Date: Wed, 22 Jan 2025 20:28:36 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 23 January 2025 04:28:40 UTC
Thanks @domenic to share the guidance for limits and suggestions. > So I think the ideal would be if all implementations were willing to pick a specific limit, and support everything in the range [0, thatLimit]. For both number of rules and depth of rules. Considering the current phase and usage, we'd like to pursue this option. As Domenic mentioned only having a lower limit doesn't solve the interop concern. > Concrete numbers can be discussed later, but I believe the specification should mention that addRoutes() may raise if the number of rules or depth of rules exceed the limitation. Agree. That's said, we need concrete numbers as long as the spec mentions limitations, right? I wonder if the numbers that Chrome is currently using (256 for the max length of rules, 10 is the max depth) are the good start to be written in the spec. Chrome doesn't see any usage exceeding those limits so far. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1746#issuecomment-2608828135 You are receiving this because you are subscribed to this thread. Message ID: <w3c/ServiceWorker/issues/1746/2608828135@github.com>
Received on Thursday, 23 January 2025 04:28:40 UTC