BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20241016T222357Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20231105T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20241103T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240310T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:299bd998-7182-481e-8734-b7f263aff25a
DTSTAMP:20241016T222357Z
SUMMARY:New Features for the ServiceWorker Performance
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/299bd998-7182-481e-8734-b7f2
 63aff25a/\n\nThe session is going to be a presentation part and discussion
  part.\n\n\nIn the [TPAC 2023 breakout](https://www.w3.org/events/meetings
 /04625253-cec9-4c78-8c17-b1fea5c50d23/)\, the Google Chrome browser team s
 hared recent efforts on [ServiceWorker](https://w3c.github.io/ServiceWorke
 r/) and discussed potential opportunities for making ServiceWorker even fa
 ster. This year\, we’d like to present a couple of updates from last yea
 r\, including a newly shipped feature called [Static Routing API](https://
 github.com/WICG/service-worker-static-routing-api)\, the new proposal exte
 nding [Resource Timing API](https://github.com/WICG/service-worker-static-
 routing-api/blob/main/resource-timing-api.md) for the Static Routing API\,
  and some of future ideas like or [ServiceWorkerAutoPreload](https://githu
 b.com/explainers-by-googlers/service-worker-auto-preload).\n\n\nFor the fi
 rst half of the session\, we’re going to present performance problems ar
 ound ServiceWorker and introduce new APIs and how it works. For the second
  half\, we’d like to spend time on the discussion.\n\nAgenda\n\n**Chairs
 :**\nShunya Shishido\, Keita Suzuki\n\n**Description:**\nThe session is go
 ing to be a presentation part and discussion part.\n\n\nIn the [TPAC 2023 
 breakout](https://www.w3.org/events/meetings/04625253-cec9-4c78-8c17-b1fea
 5c50d23/)\, the Google Chrome browser team shared recent efforts on [Servi
 ceWorker](https://w3c.github.io/ServiceWorker/) and discussed potential op
 portunities for making ServiceWorker even faster. This year\, we’d like 
 to present a couple of updates from last year\, including a newly shipped 
 feature called [Static Routing API](https://github.com/WICG/service-worker
 -static-routing-api)\, the new proposal extending [Resource Timing API](ht
 tps://github.com/WICG/service-worker-static-routing-api/blob/main/resource
 -timing-api.md) for the Static Routing API\, and some of future ideas like
  or [ServiceWorkerAutoPreload](https://github.com/explainers-by-googlers/s
 ervice-worker-auto-preload).\n\n\nFor the first half of the session\, we
 ’re going to present performance problems around ServiceWorker and intro
 duce new APIs and how it works. For the second half\, we’d like to spend
  time on the discussion.\n\n**Goal(s):**\nThis session aims to discuss Ser
 viceWorkers performance issues\, and how we can mitigate them.  For the st
 atic routing API (now it’s part of the ServiceWorker spec)\, we’d like
  to hear browser vender status. For the other APIs that we’re proposing\
 , we’d like to discuss and gather feedback from the community to make th
 e standardization process forward.\n\n\n\n**Materials:**\n- [slides](https
 ://www.w3.org/2024/Talks/TPAC/breakouts/sw-for-performance.pdf)\n- [minute
 s](https://www.w3.org/2024/09/25-serviceworkers-minutes.html)\n- [Session 
 proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/17)\n
 \n**Track(s):**\n- Web Apps
STATUS:CONFIRMED
CREATED:20240916T214913Z
LAST-MODIFIED:20241016T222357Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR