BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2026//talk//MDJWSA
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-cz-2026-MDJWSA@pretalx.devconf.info
DTSTART;TZID=CET:20260618T110000
DTEND;TZID=CET:20260618T113500
DESCRIPTION:In today's modern internet transport landscape\, HTTP/3 and QUI
 C are often presented as the next step in the evolution of web transport\,
  promising lower latency and improved multiplexing. However\, adopting QUI
 C is not just a protocol upgrade - it fundamentally reshapes how applicati
 on stacks\, networking layers\, and infrastructure interact.\n\nIn this ta
 lk we explore how QUIC and HTTP/3 change the traditional layering between 
 transport\, TLS\, and application protocols. Using practical examples from
  working with HTTP/3 implementations across the stack - deployments with `
 nginx` and client-side experimentation with `curl` - we look at what it me
 ans to integrate QUIC into existing infrastructure. Topics include connect
 ion management\, retry semantics\, operational visibility\, and performanc
 e trade-offs when introducing QUIC into production environments.\n\nFinall
 y\, we discuss how QUIC’s architecture enables a gradual unification of 
 the tech stack around shared transport abstractions.
DTSTAMP:20260430T125107Z
LOCATION:E105 (capacity 70)
SUMMARY:On QUIC\, HTTP/3 and tech stack unification - Gabriel Michael Homa
URL:https://pretalx.devconf.info/devconf-cz-2026/talk/MDJWSA/
END:VEVENT
END:VCALENDAR