<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reading List</title>
    <link>https://reading-list.oddship.net</link>
    <description>A curated linklog of essays, posts, papers, and notes.</description>
    <atom:link href="https://reading-list.oddship.net/tags/go/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Thu, 15 Oct 2026 10:08:00 +0530</lastBuildDate>
    
      <item>
        <title>Go 1.27 improves HTTP&#x2F;1 connection reuse</title>
        <link>https://reading-list.oddship.net/notes/2026-10-15-go-http-connection-reuse/</link>
        <guid>https://reading-list.oddship.net/notes/2026-10-15-go-http-connection-reuse/</guid>
        <pubDate>Thu, 15 Oct 2026 10:08:00 +0530</pubDate>
        <description>Logged at IST: 2026-10-15 10:08 IST
What it is: A Go blog article by Nicholas Husin and Damien Neil describing improved HTTP&amp;amp;#x2F;1 connection reuse in Go 1.27.
Gist: In earlier Go versions, an HTTP&amp;amp;#x2F;1 connection could be discarded when a caller closed a response body with unread bytes. Go 1.27&amp;amp;#x27;s net&amp;amp;#x2F;http.Transport asynchronously drains a limited amount, up to 256 KB or 50 ms, to salvage reuse. The article reports roughly a 5× improvement in its repeated-request benchmark. Callers can keep closing response bodies as usual; HTTP&amp;amp;#x2F;2 was not affected by this particular issue.
Why it matters: A useful pe…</description>
      </item>
    
  </channel>
</rss>
