<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/www/http-parser/PLIST, branch trunk</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2016-08-25T18:30:33Z</updated>
<entry>
<title>Use libtool for the build and install.  Fixes various issues with the</title>
<updated>2016-08-25T18:30:33Z</updated>
<author>
<name>jperkin</name>
<email>jperkin@pkgsrc.org</email>
</author>
<published>2016-08-25T18:30:33Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=afe3f372f4d8147aaceb2d89af7d72d1baaafdfd'/>
<id>urn:sha1:afe3f372f4d8147aaceb2d89af7d72d1baaafdfd</id>
<content type='text'>
package which meant it only worked on NetBSD.  Bump PKGREVISION.</content>
</entry>
<entry>
<title>Simplify by using more of the github framework.</title>
<updated>2016-05-29T14:17:48Z</updated>
<author>
<name>wiz</name>
<email>wiz@pkgsrc.org</email>
</author>
<published>2016-05-29T14:17:48Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=4562e16142552df8de88a7843125e84114979439'/>
<id>urn:sha1:4562e16142552df8de88a7843125e84114979439</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add www/http-parser 2.7.0.</title>
<updated>2016-05-28T23:09:30Z</updated>
<author>
<name>schnoebe</name>
<email>schnoebe@pkgsrc.org</email>
</author>
<published>2016-05-28T23:09:30Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=6c5e322ab4a13210b8374f137cefce9881a5b5ba'/>
<id>urn:sha1:6c5e322ab4a13210b8374f137cefce9881a5b5ba</id>
<content type='text'>
An parser for HTTP messages written in C, parsing both requests
and responses. It is designed to be used in performance oriented
HTTP applications. It does not make any syscalls nor allocations,
it does not buffer data, it can be interrupted at anytime. Depending
on your architecture, it only requires about 40 bytes of data per
message stream (in a web server that is per connection).</content>
</entry>
</feed>
