<?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: another nsopenssl-related memory leak fixed!</title>
	<atom:link href="http://dossy.org/2005/03/another-nsopensslrelated-memory-leak-fixed/feed/" rel="self" type="application/rss+xml" />
	<link>http://dossy.org/2005/03/another-nsopensslrelated-memory-leak-fixed/</link>
	<description>Everything that comes out of Dossy, from the strange to the banal.</description>
	<lastBuildDate>Fri, 20 Nov 2009 01:35:37 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dossy</title>
		<link>http://dossy.org/2005/03/another-nsopensslrelated-memory-leak-fixed/comment-page-1/#comment-99</link>
		<dc:creator>Dossy</dc:creator>
		<pubDate>Wed, 12 Oct 2005 18:22:37 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000108.html#comment-99</guid>
		<description>At this point, I would suggest just using the tip of the aolserver_v40_bp branch -- eventually, that will be tagged and released as AOLserver 4.0.11.

Side-effects of setting &quot;keepalivetimeout&quot; to 0?  Just that, well, HTTP Keep-Alive will be disabled.  This might result in a small performance impact, as clients will need to initiate full TCP connections to the server per HTTP request rather than reusing an existing connection.  This is likely to be a non-issue in real-world sites, though.</description>
		<content:encoded><![CDATA[<p>At this point, I would suggest just using the tip of the aolserver_v40_bp branch &#8212; eventually, that will be tagged and released as AOLserver 4.0.11.</p>
<p>Side-effects of setting &#8220;keepalivetimeout&#8221; to 0?  Just that, well, HTTP Keep-Alive will be disabled.  This might result in a small performance impact, as clients will need to initiate full TCP connections to the server per HTTP request rather than reusing an existing connection.  This is likely to be a non-issue in real-world sites, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rocael Hernandez</title>
		<link>http://dossy.org/2005/03/another-nsopensslrelated-memory-leak-fixed/comment-page-1/#comment-98</link>
		<dc:creator>Rocael Hernandez</dc:creator>
		<pubDate>Wed, 12 Oct 2005 17:14:44 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000108.html#comment-98</guid>
		<description>It is possible to use aolserver/nsd/driver.c with the memory leak fixed with the actual 4.0.10 distro?

Also, what side effects might carry?:
ns_param    keepalivetimeout    0</description>
		<content:encoded><![CDATA[<p>It is possible to use aolserver/nsd/driver.c with the memory leak fixed with the actual 4.0.10 distro?</p>
<p>Also, what side effects might carry?:<br />
ns_param    keepalivetimeout    0</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.395 seconds -->
