<story><title>Httpserver.h: Single header library for writing non-blocking HTTP servers in C</title><url>https://github.com/jeremycw/httpserver.h</url></story><parent_chain></parent_chain><comment><author>_bxg1</author><text>Question: I thought any given C code could go in either headers or c files (or rather, split between headers and c files), and that the difference was only a build concern. So why wouldn&amp;#x27;t a given library be available in both forms, unless one of them just makes no sense at all? Put differently: why isn&amp;#x27;t this just &amp;quot;Minimal library for writing non-blocking HTTP servers in C&amp;quot; which people understand to mean &amp;quot;this might make sense to put in a header&amp;quot;?</text></comment>
<story><title>Httpserver.h: Single header library for writing non-blocking HTTP servers in C</title><url>https://github.com/jeremycw/httpserver.h</url></story><parent_chain></parent_chain><comment><author>maxk42</author><text>h2o [1] is a web server and C library that not only supports http 1 &amp;amp; 2, but also usually tops the TechEmpower benchmarks [2].&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;h2o&amp;#x2F;h2o&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;h2o&amp;#x2F;h2o&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.techempower.com&amp;#x2F;benchmarks&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.techempower.com&amp;#x2F;benchmarks&amp;#x2F;&lt;/a&gt;</text></comment>