<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Parsing HTTP Headers</title>
	<atom:link href="http://www.dereferenced.com/2009/09/13/parsing-http-headers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dereferenced.com/2009/09/13/parsing-http-headers/</link>
	<description>A preponderance of Perl, an excess of XML, and additional alliterations.</description>
	<lastBuildDate>Thu, 19 Jan 2012 08:50:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dereferenced.com &#187; Blog Archive &#187; Perl Module Monday: HTTP Parsing Triple-Play</title>
		<link>http://www.dereferenced.com/2009/09/13/parsing-http-headers/comment-page-1/#comment-36</link>
		<dc:creator>Dereferenced.com &#187; Blog Archive &#187; Perl Module Monday: HTTP Parsing Triple-Play</dc:creator>
		<pubDate>Tue, 15 Sep 2009 05:12:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.dereferenced.com/?p=51#comment-36</guid>
		<description>[...] little bit and actually look at three modules. All of these address the same basic problem, which I wrote about yesterday: parsing HTTP [...]</description>
		<content:encoded><![CDATA[<p>[...] little bit and actually look at three modules. All of these address the same basic problem, which I wrote about yesterday: parsing HTTP [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rjray</title>
		<link>http://www.dereferenced.com/2009/09/13/parsing-http-headers/comment-page-1/#comment-35</link>
		<dc:creator>rjray</dc:creator>
		<pubDate>Mon, 14 Sep 2009 19:51:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.dereferenced.com/?p=51#comment-35</guid>
		<description>I saw both HTTP::Parser::XS and HTTP::HeaderParser::XS after I took the steps to move in and help with HTTP::Parser.

Ideally, I&#039;d like to see this package be a wrapper that selects between a pure-Perl solution (perhaps HTTP::Parser::PP) and HTTP::Parser::XS, based on availability. That is, IDEALLY I&#039;d like to see this become flexible-enough and useful-enough that Plack, Catalyst, etc. are able to plug it in.</description>
		<content:encoded><![CDATA[<p>I saw both HTTP::Parser::XS and HTTP::HeaderParser::XS after I took the steps to move in and help with HTTP::Parser.</p>
<p>Ideally, I&#8217;d like to see this package be a wrapper that selects between a pure-Perl solution (perhaps HTTP::Parser::PP) and HTTP::Parser::XS, based on availability. That is, IDEALLY I&#8217;d like to see this become flexible-enough and useful-enough that Plack, Catalyst, etc. are able to plug it in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tatsuhiko Miyagawa</title>
		<link>http://www.dereferenced.com/2009/09/13/parsing-http-headers/comment-page-1/#comment-34</link>
		<dc:creator>Tatsuhiko Miyagawa</dc:creator>
		<pubDate>Mon, 14 Sep 2009 08:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dereferenced.com/?p=51#comment-34</guid>
		<description>Heh, cool that we come across the same thing: today Kazuho Oku shipped HTTP::Parser::XS to CPAN, that stops after the header parsing is done, and yeah, I created Plack::HTTPParser::PP which is a copy of HTTP::Parser but has the same interface with his new XS module. Take a look.

(There is also HTTP::HeaderParser::XS, which Catalyst and Perlbal uses)</description>
		<content:encoded><![CDATA[<p>Heh, cool that we come across the same thing: today Kazuho Oku shipped HTTP::Parser::XS to CPAN, that stops after the header parsing is done, and yeah, I created Plack::HTTPParser::PP which is a copy of HTTP::Parser but has the same interface with his new XS module. Take a look.</p>
<p>(There is also HTTP::HeaderParser::XS, which Catalyst and Perlbal uses)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
