<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>if you want something done right... DIY.</title>
	<link>http://krisgale.com</link>
	<description>meanderings of a computer scientist on the brink of sheer insanity.</description>
	<pubDate>Tue, 24 Nov 2009 20:22:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>
	<language>en</language>
			<item>
		<title>fread() without $length causes internal server error</title>
		<link>http://krisgale.com/fread-without-length-causes-internal-server-error/</link>
		<comments>http://krisgale.com/fread-without-length-causes-internal-server-error/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 20:22:07 +0000</pubDate>
		<dc:creator>krisgale</dc:creator>
		
		<category><![CDATA[oddities]]></category>

		<category><![CDATA[php]]></category>

		<category><![CDATA[apache]]></category>

		<guid isPermaLink="false">http://krisgale.com/fread-without-length-causes-internal-server-error/</guid>
		<description><![CDATA[and here i thought php would supply a default value for the second parameter to fread(), namely the number of bytes to be read from an open file handle (that being the first parameter). nope! not only does this quietly surpass php&#8217;s syntax check, it causes an internal server error thus creating quite the air [...]]]></description>
			<content:encoded><![CDATA[<p>and here i thought php would supply a default value for the second parameter to fread(), namely the number of bytes to be read from an open file handle (that being the first parameter). nope! not only does this quietly surpass php&#8217;s syntax check, it causes an internal server error thus creating quite the air of mystery as to what went wrong.</p>
]]></content:encoded>
			<wfw:commentRss>http://krisgale.com/fread-without-length-causes-internal-server-error/feed/</wfw:commentRss>
		</item>
		<item>
		<title>sitepoint&#8217;s twitter-giveaway: interesting myisam vs. innodb case study</title>
		<link>http://krisgale.com/sitepoints-twitter-giveaway-interesting-myisam-vs-innodb-case-study/</link>
		<comments>http://krisgale.com/sitepoints-twitter-giveaway-interesting-myisam-vs-innodb-case-study/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 21:32:33 +0000</pubDate>
		<dc:creator>krisgale</dc:creator>
		
		<category><![CDATA[best practice]]></category>

		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://krisgale.com/sitepoints-twitter-giveaway-interesting-myisam-vs-innodb-case-study/</guid>
		<description><![CDATA[sitepoint recently discovered when and why row-level locking (as opposed to table-level) is sometimes a must-have&#8230;
http://www.sitepoint.com/blogs/2009/09/08/free-performance-with-mysql-table-types/
]]></description>
			<content:encoded><![CDATA[<p>sitepoint recently discovered when and why row-level locking (as opposed to table-level) is sometimes a must-have&#8230;</p>
<p><a href="http://www.sitepoint.com/blogs/2009/09/08/free-performance-with-mysql-table-types/" target="_blank">http://www.sitepoint.com/blogs/2009/09/08/free-performance-with-mysql-table-types/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://krisgale.com/sitepoints-twitter-giveaway-interesting-myisam-vs-innodb-case-study/feed/</wfw:commentRss>
		</item>
		<item>
		<title>payflow pro critical update 9/1</title>
		<link>http://krisgale.com/payflow-pro-critical-update-91/</link>
		<comments>http://krisgale.com/payflow-pro-critical-update-91/#comments</comments>
		<pubDate>Mon, 10 Aug 2009 03:54:04 +0000</pubDate>
		<dc:creator>krisgale</dc:creator>
		
		<category><![CDATA[ecommerce]]></category>

		<category><![CDATA[web hosting]]></category>

		<guid isPermaLink="false">http://krisgale.com/payflow-pro-critical-update-91/</guid>
		<description><![CDATA[for those of you out there charged with developing/maintaining ecommerce sites using verisign/paypal’s “payflow pro” interface, be aware that as of september 1st (yes, three weeks away) older versions of their sdk will no longer be supported.
information about the upgrade (and instructions on how to perform the required code changes to your site(s)) can be [...]]]></description>
			<content:encoded><![CDATA[<p class="formatted_text_body">for those of you out there charged with developing/maintaining ecommerce sites using verisign/paypal’s “payflow pro” interface, be aware that as of september 1st (yes, three weeks away) older versions of their sdk will no longer be supported.</p>
<p>information about the upgrade (and instructions on how to perform the required code changes to your site(s)) can be found here:</p>
<p><a href="http://integrationwizard.x.com/sdkupdate/step1.php">http://integrationwizard.x.com/sdkupdate/step1.php</a></p>
<p>good luck.</p>
<p>p.s. this might be a good opportunity to switch to authorizenet since the newer payflow pro sdk uses Very Similar ‘silent’ https post’s to/from the gateway server (as opposed to an intermediary native-code binary in older versions) and might even save you/your client(s) some money, since the two gateways&#8217; pricing structures vary when it comes to per-transaction fees and minimum/maximum sales volume thresholds. have that conversation with your merchant services provider.</p>
]]></content:encoded>
			<wfw:commentRss>http://krisgale.com/payflow-pro-critical-update-91/feed/</wfw:commentRss>
		</item>
		<item>
		<title>scheduling: maker vs. manager</title>
		<link>http://krisgale.com/scheduling-maker-vs-manager/</link>
		<comments>http://krisgale.com/scheduling-maker-vs-manager/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 19:50:15 +0000</pubDate>
		<dc:creator>krisgale</dc:creator>
		
		<category><![CDATA[best practice]]></category>

		<category><![CDATA[project management]]></category>

		<guid isPermaLink="false">http://krisgale.com/scheduling-maker-vs-manager/</guid>
		<description><![CDATA[really interesting article outlining the core issues surrounding managers&#8217; scheduling of meetings from a maker&#8217;s perspective, with some ideas towards a solution.
&#8220;We know we have to have some number of meetings. All we ask from those on the manager&#8217;s schedule is that they understand the cost.&#8221;
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.paulgraham.com/makersschedule.html" target="_blank">really interesting article</a> outlining the core issues surrounding managers&#8217; scheduling of meetings from a maker&#8217;s perspective, with some ideas towards a solution.</p>
<p>&#8220;We know we have to have some number of meetings. All we ask from those on the manager&#8217;s schedule is that they understand the cost.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://krisgale.com/scheduling-maker-vs-manager/feed/</wfw:commentRss>
		</item>
		<item>
		<title>sick of using vi to edit crontab?</title>
		<link>http://krisgale.com/sick-of-using-vi-to-edit-crontab/</link>
		<comments>http://krisgale.com/sick-of-using-vi-to-edit-crontab/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 17:02:22 +0000</pubDate>
		<dc:creator>krisgale</dc:creator>
		
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://krisgale.com/sick-of-using-vi-to-edit-crontab/</guid>
		<description><![CDATA[use any editor of your choosing to modify crontab&#8230;  at your command prompt (assuming you are root), type:
EDITOR=nano
export EDITOR
now, when you crontab -e that editor (in this case, nano) will be used instead of vi. what a relief!
]]></description>
			<content:encoded><![CDATA[<p>use any editor of your choosing to modify crontab&#8230;  at your command prompt (assuming you are root), type:</p>
<p><tt>EDITOR=nano<br />
export EDITOR</tt></p>
<p>now, when you <tt>crontab -e</tt> that editor (in this case, nano) will be used instead of vi. what a relief!</p>
]]></content:encoded>
			<wfw:commentRss>http://krisgale.com/sick-of-using-vi-to-edit-crontab/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
