BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20230919T112954Z
BEGIN:VTIMEZONE
TZID:Europe/Madrid
BEGIN:STANDARD
DTSTART:20221030T010000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:STANDARD
DTSTART:20231029T010000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20230326T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:04625253-cec9-4c78-8c17-b1fea5c50d23
DTSTAMP:20230919T112954Z
SUMMARY:ServiceWorker and Loading Performance
DTSTART;TZID=Europe/Madrid:20230913T121500
DTEND;TZID=Europe/Madrid:20230913T131500
DESCRIPTION:https://www.w3.org/events/meetings/04625253-cec9-4c78-8c17-b1fe
 a5c50d23/\n\nThe session is going to be a presentation part and discussion
  part.\n\n\n\n\n\n\n\nStarting ServiceWorkers is known to be a slow proces
 s\, and web users need to wait for its startup if the ServiceWorker interc
 epts loading the page resources. At the same time\, the ServiceWorker brin
 gs flexibility to the transport layer\, and it behaves as a client-side pr
 oxy. Developers can implement offline support or provide client-side conte
 nt modification with it.\n\n\n\n\n\n\n\nWe have a couple of early ideas to
  minimize the performance cost\, such as [the static routing API](https://
 github.com/yoshisatoyanagisawa/service-worker-static-routing-api)\, and [s
 kip no-op fetch handler](https://github.com/yoshisatoyanagisawa/service-wo
 rker-skip-no-op-fetch-handler). For the first half of the session\, we’r
 e going to present performance problems that we’re observing\, outline o
 f proposed APIs and how it works\, and estimated performance improvements.
 \n\n\n\n\n\n\n\nFor the second half\, we’d like to discuss ServiceWorker
  and performance with the community and ask for feedback on our ideas.\n\n
 Agenda\n\n**Chairs:**\nShunya Shishido\n\n**Description:**\nThe session is
  going to be a presentation part and discussion part.\n\n\n\n\n\n\n\nStart
 ing ServiceWorkers is known to be a slow process\, and web users need to w
 ait for its startup if the ServiceWorker intercepts loading the page resou
 rces. At the same time\, the ServiceWorker brings flexibility to the trans
 port layer\, and it behaves as a client-side proxy. Developers can impleme
 nt offline support or provide client-side content modification with it.\n\
 n\n\n\n\n\n\nWe have a couple of early ideas to minimize the performance c
 ost\, such as [the static routing API](https://github.com/yoshisatoyanagis
 awa/service-worker-static-routing-api)\, and [skip no-op fetch handler](ht
 tps://github.com/yoshisatoyanagisawa/service-worker-skip-no-op-fetch-handl
 er). For the first half of the session\, we’re going to present performa
 nce problems that we’re observing\, outline of proposed APIs and how it 
 works\, and estimated performance improvements.\n\n\n\n\n\n\n\nFor the sec
 ond half\, we’d like to discuss ServiceWorker and performance with the c
 ommunity and ask for feedback on our ideas.\n\n**Goal(s):**\nThis session 
 aims to discuss and learn about ServiceWorkers performance issues. We’re
  going to present some newly proposed ServiceWorker APIs and optimizations
  to address performance issues as well\, we’d like to discuss and gather
  feedback from the community.\n\n\n**Materials:**\n- [slides](https://docs
 .google.com/presentation/d/1aoHncqpr-3bC-Wh5yVjL1WO5YHyFiwTdarzDMjdwpuU/ed
 it#slide=id.p)\n- [minutes](https://www.w3.org/2023/09/13-serviceworkers-m
 inutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac20
 23-breakouts/issues/7)\n\n**Track(s):**\n- performance
STATUS:CONFIRMED
CREATED:20230905T053545Z
LAST-MODIFIED:20230919T112954Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Nervion I - Level -1
CATEGORIES:TPAC 2023,Breakout Sessions
END:VEVENT
END:VCALENDAR