<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Protocol Buffers – Missing Usage Guide?</title>
	<atom:link href="http://lsblog.wordpress.com/2008/07/14/protocol-buffers-%e2%80%93-missing-usage-guide/feed/" rel="self" type="application/rss+xml" />
	<link>http://lsblog.wordpress.com/2008/07/14/protocol-buffers-%e2%80%93-missing-usage-guide/</link>
	<description>Random thoughts about software, trading and live</description>
	<lastBuildDate>Thu, 10 Sep 2009 22:39:47 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: libor</title>
		<link>http://lsblog.wordpress.com/2008/07/14/protocol-buffers-%e2%80%93-missing-usage-guide/#comment-2852</link>
		<dc:creator>libor</dc:creator>
		<pubDate>Wed, 22 Oct 2008 22:28:01 +0000</pubDate>
		<guid isPermaLink="false">http://lsblog.wordpress.com/?p=37#comment-2852</guid>
		<description>HTTP is stateless protocol. Each request might start with making/opening TCP connection and than sending request to the server side.

So you have perf. degradation right there.

Additionally you have to parse text based HTML header to know binary data are send over.

I agree for the most cases this probably does not matter much but in real-time or large number transaction systems (i.e. GOOGLE like case) even such overheads will magnify total results.</description>
		<content:encoded><![CDATA[<p>HTTP is stateless protocol. Each request might start with making/opening TCP connection and than sending request to the server side.</p>
<p>So you have perf. degradation right there.</p>
<p>Additionally you have to parse text based HTML header to know binary data are send over.</p>
<p>I agree for the most cases this probably does not matter much but in real-time or large number transaction systems (i.e. GOOGLE like case) even such overheads will magnify total results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bmadigan</title>
		<link>http://lsblog.wordpress.com/2008/07/14/protocol-buffers-%e2%80%93-missing-usage-guide/#comment-2849</link>
		<dc:creator>bmadigan</dc:creator>
		<pubDate>Thu, 09 Oct 2008 15:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://lsblog.wordpress.com/?p=37#comment-2849</guid>
		<description>How does HTTP negate performance gains of binary format vs character format? You generally read the content as a byte stream, so setting the content-type and content-encoding properly should prevent any problems.</description>
		<content:encoded><![CDATA[<p>How does HTTP negate performance gains of binary format vs character format? You generally read the content as a byte stream, so setting the content-type and content-encoding properly should prevent any problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-07-15 &#171; Breyten&#8217;s Dev Blog</title>
		<link>http://lsblog.wordpress.com/2008/07/14/protocol-buffers-%e2%80%93-missing-usage-guide/#comment-2845</link>
		<dc:creator>links for 2008-07-15 &#171; Breyten&#8217;s Dev Blog</dc:creator>
		<pubDate>Tue, 15 Jul 2008 11:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://lsblog.wordpress.com/?p=37#comment-2845</guid>
		<description>[...] Protocol Buffers ? Missing Usage Guide? &quot; Libor.SOUCEK(&quot;WEBLog&amp;quot   (tags: distributed-computing google) [...]</description>
		<content:encoded><![CDATA[<p>[...] Protocol Buffers ? Missing Usage Guide? &quot; Libor.SOUCEK(&quot;WEBLog&#38;quot   (tags: distributed-computing google) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
