<?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: pycon 2008 &#8211; day 2</title>
	<atom:link href="http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/</link>
	<description>random ramblings about nerdy things</description>
	<lastBuildDate>Fri, 09 Jul 2010 11:38:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gene Oden</title>
		<link>http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/comment-page-1/#comment-60</link>
		<dc:creator>Gene Oden</dc:creator>
		<pubDate>Wed, 26 Mar 2008 17:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/#comment-60</guid>
		<description>thanks, i appreciate the work you&#039;ve put into this and stackless.

i haven&#039;t taken the time to build a patch from our latest changes or merge &amp; test your latest changes but i should be able to do that in the next week or two.

i have a copy of our latest version here:

http://eugeneoden.com/stacklesssocket.py

looking at a diff between that and what i think is the original before my changes i can&#039;t recall exactly why i made some of the changes for add_channel().

the timer stuff is modeled after another variant of non-blocking io found here:

http://sweetbytes.net/stackless_io.html

and works well for us.  this reduced the busy-waiting of the process considerably.</description>
		<content:encoded><![CDATA[<p>thanks, i appreciate the work you&#8217;ve put into this and stackless.</p>
<p>i haven&#8217;t taken the time to build a patch from our latest changes or merge &#038; test your latest changes but i should be able to do that in the next week or two.</p>
<p>i have a copy of our latest version here:</p>
<p><a href="http://eugeneoden.com/stacklesssocket.py" rel="nofollow">http://eugeneoden.com/stacklesssocket.py</a></p>
<p>looking at a diff between that and what i think is the original before my changes i can&#8217;t recall exactly why i made some of the changes for add_channel().</p>
<p>the timer stuff is modeled after another variant of non-blocking io found here:</p>
<p><a href="http://sweetbytes.net/stackless_io.html" rel="nofollow">http://sweetbytes.net/stackless_io.html</a></p>
<p>and works well for us.  this reduced the busy-waiting of the process considerably.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Tew</title>
		<link>http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/comment-page-1/#comment-52</link>
		<dc:creator>Richard Tew</dc:creator>
		<pubDate>Tue, 25 Mar 2008 12:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/#comment-52</guid>
		<description>I should add I fixed the closing problem mentioned in my previous comment last night.</description>
		<content:encoded><![CDATA[<p>I should add I fixed the closing problem mentioned in my previous comment last night.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Tew</title>
		<link>http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/comment-page-1/#comment-49</link>
		<dc:creator>Richard Tew</dc:creator>
		<pubDate>Mon, 24 Mar 2008 15:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/#comment-49</guid>
		<description>Yes, stacklesssocket isn&#039;t really a solution which should be picked up and trusted to be solid or correct.  As time goes by, its incompatibilities with normal socket behaviour become more and more obvious.

My recent changes are not necessarily reliable.  At this time the biggest bug is that if the socket is closed, then the socket is really closed rather than remaining open for file objects created from it to use.

Fixes or patches to it would be appreciated.  As it is, I just have to find the time and interest to work on it when I can in my free time :-)</description>
		<content:encoded><![CDATA[<p>Yes, stacklesssocket isn&#8217;t really a solution which should be picked up and trusted to be solid or correct.  As time goes by, its incompatibilities with normal socket behaviour become more and more obvious.</p>
<p>My recent changes are not necessarily reliable.  At this time the biggest bug is that if the socket is closed, then the socket is really closed rather than remaining open for file objects created from it to use.</p>
<p>Fixes or patches to it would be appreciated.  As it is, I just have to find the time and interest to work on it when I can in my free time :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gene Oden</title>
		<link>http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/comment-page-1/#comment-29</link>
		<dc:creator>Gene Oden</dc:creator>
		<pubDate>Mon, 17 Mar 2008 04:11:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/#comment-29</guid>
		<description>on day 1 they had these pre-packaged meals with a ham or veggie sandwich - i had the ham but probably should have gone with the veggie.  day 2 they had a buffet with bbq pork sandwiches or something like that.  i didn&#039;t eat much of the pork and with my headache now and am regretting that i had any of it.</description>
		<content:encoded><![CDATA[<p>on day 1 they had these pre-packaged meals with a ham or veggie sandwich &#8211; i had the ham but probably should have gone with the veggie.  day 2 they had a buffet with bbq pork sandwiches or something like that.  i didn&#8217;t eat much of the pork and with my headache now and am regretting that i had any of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Kirk</title>
		<link>http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/comment-page-1/#comment-28</link>
		<dc:creator>Brian Kirk</dc:creator>
		<pubDate>Mon, 17 Mar 2008 03:54:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eugeneoden.com/2008/03/15/pycon-2008-day-2/#comment-28</guid>
		<description>what was for lunch on day 2 that made it better than day 1? let me guess - pizza or wraps?

you should definitely submit the work you &amp; smitty did for stackless.

tripping over podiums &amp; possessed PCs  - sounds like a day at our office only worse - tripping over power chords connecting to switches &amp; power vaults are the possessed pieces of equipment these days.</description>
		<content:encoded><![CDATA[<p>what was for lunch on day 2 that made it better than day 1? let me guess &#8211; pizza or wraps?</p>
<p>you should definitely submit the work you &amp; smitty did for stackless.</p>
<p>tripping over podiums &amp; possessed PCs  &#8211; sounds like a day at our office only worse &#8211; tripping over power chords connecting to switches &amp; power vaults are the possessed pieces of equipment these days.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
