<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [Desktop][Developer] CDN API support HTTP/2 in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5317223#M3800</link>
    <description>&lt;P&gt;Agreed - HTTP/2 would be great!&lt;/P&gt;</description>
    <pubDate>Sat, 18 Dec 2021 08:45:13 GMT</pubDate>
    <dc:creator>DONTBLINKMUSIC</dc:creator>
    <dc:date>2021-12-18T08:45:13Z</dc:date>
    <item>
      <title>[Desktop][Developer] CDN API support HTTP/2</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5295864#M3640</link>
      <description>&lt;P&gt;There was &lt;A href="https://github.com/spotify/web-api/issues/803" target="_self"&gt;an issue&lt;/A&gt; in the WebAPI github repo in the past where HTTP/2 support was mentioned, but the same was never mentioned again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any way to get feedback or a possible implementation of the issue?&lt;/P&gt;&lt;P&gt;HTTP/2 is considered a standard these days, and improve the performance of the image CDN&lt;/P&gt;</description>
      <pubDate>Tue, 16 Nov 2021 10:32:23 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5295864#M3640</guid>
      <dc:creator>heatmanofurioso</dc:creator>
      <dc:date>2021-11-16T10:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: [Desktop][Developer] CDN API support HTTP/2</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5317223#M3800</link>
      <description>&lt;P&gt;Agreed - HTTP/2 would be great!&lt;/P&gt;</description>
      <pubDate>Sat, 18 Dec 2021 08:45:13 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5317223#M3800</guid>
      <dc:creator>DONTBLINKMUSIC</dc:creator>
      <dc:date>2021-12-18T08:45:13Z</dc:date>
    </item>
    <item>
      <title>Re: [Desktop][Developer] CDN API support HTTP/2</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5333419#M4000</link>
      <description>&lt;P class=""&gt;This actually also applies to the embeddable widget, and even Spotify's own web player and app that open individual slow http/1.1 connections for each cover artwork that is being fetched. Feels like a no brainer of an optimization, especially as it should be a fairly easy change within the CDN config. In fact, Fastly already supports HTTP/3 and QUIC now.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jan 2022 08:30:48 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5333419#M4000</guid>
      <dc:creator>DONTBLINKMUSIC</dc:creator>
      <dc:date>2022-01-27T08:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: [Desktop][Developer] CDN API support HTTP/2</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5420902#M5478</link>
      <description>&lt;P&gt;Any news on this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's probably a matter of switching on a config.. with no impact on costs, or business.. that will improve performance &amp;amp; security on the product, as well on any dependants of it.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2022 13:13:03 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Desktop-Developer-CDN-API-support-HTTP-2/m-p/5420902#M5478</guid>
      <dc:creator>heatmanofurioso</dc:creator>
      <dc:date>2022-08-24T13:13:03Z</dc:date>
    </item>
  </channel>
</rss>

