BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//DRXC3E
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-europython-2026-DRXC3E@programme.europython.eu
DTSTART;TZID=CET:20260715T135000
DTEND;TZID=CET:20260715T142000
DESCRIPTION:# Python and HTTP/3: feel the difference in performance\n\n## A
 bstract\n\nBuilding real-time Python applications\, from live dashboards t
 o multiplayer games\, often feels like a battle against an invisible lag. 
 While we focus on optimizing our async code\, the underlying transport pro
 tocol often sabotages us: `TCP` guarantees ordering at the absolute cost o
 f responsiveness.\n\nIn this session\, I will show that the standard choic
 e of using Websocket over `HTTP/1.1` or `HTTP/2` can make the application 
 perform horribly\, due to the "head-of-line blocking" problem that is visi
 ble when the network is unstable.\nThen I will present how `HTTP/3` and `W
 ebTransport` eliminate transport-layer bottlenecks and enable seamless con
 nection migration for network switching users.\nThe audience will experien
 ce the difference between protocols performance firsthand through a live t
 hree-round multiplayer snake game demo. \n\n## Description\n\n### The Prob
 lem\n\nApplication performance is a complex challenge. Users often complai
 n about lag\, and regardless of how well we optimize our business logic\, 
 the issue persists. All too often\, the blame is shifted to the client for
  having a "spotty network." However\, even under ideal conditions\, users 
 experience disruptions simply by being mobile\, due to switching between W
 i-Fi access points or cellular towers. The core problem is that many devel
 opers are unaware of the limitations of `HTTP/1.1` and `HTTP/2`\, or that 
 implementing `HTTP/3` might be a solution.\n\n### Why This is Interesting 
 to the Python Community\n\nAs Python applications become more real-time an
 d data-intensive\, traditional networking stacks are reaching their limits
 . There are important advances in technology that the audience should get 
 familiar with\, like `HTTP/3`\, `QUIC`\, and `WebTransport`. What is also 
 important\, is to be aware of how the Python ecosystem is still fragmented
  when it comes to supporting `HTTP/3`. \nDespite that\, a solution is achi
 evable\, and by using a combination of `Starlette` and `aioquic` code acro
 ss three generations of transport protocols\, the audience will experience
  and learn how protocol choice dictates application reliability on imperfe
 ct networks.\n\n### Key takeaways:\n- Witness an app suffering from transp
 ort-layer head-of-line blocking.\n- Understand the Python `HTTP/3` ecosyst
 em\, including `aioquic`\, `Hypercorn`\, and `Starlette`.\n- Deploy a `HTT
 P/3` server handling `WebTransport` datagrams for real-time data.\n- Learn
  how to use Linux traffic control (`tc`) to inject some chaos to the netwo
 rk\n- Play multiplayer Snake!
DTSTAMP:20260524T130740Z
LOCATION:Chamber Hall B (S3B)
SUMMARY:Python and HTTP/3: feel the difference in performance - Daniel Vahl
 a
URL:https://programme.europython.eu/europython-2026/talk/DRXC3E/
END:VEVENT
END:VCALENDAR