<?xml version="1.0" encoding="UTF-8"?>
<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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Vallery.net &#187; lamp</title>
	<atom:link href="http://vallery.net/tag/lamp/feed/" rel="self" type="application/rss+xml" />
	<link>http://vallery.net</link>
	<description>personal homepage of Jason Vallery</description>
	<lastBuildDate>Thu, 17 May 2012 05:21:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Debug your outbound POST and GET requests</title>
		<link>http://vallery.net/2007/05/17/debug-your-outbound-post-and-get-requests/</link>
		<comments>http://vallery.net/2007/05/17/debug-your-outbound-post-and-get-requests/#comments</comments>
		<pubDate>Thu, 17 May 2007 19:27:13 +0000</pubDate>
		<dc:creator>jvallery</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[get]]></category>
		<category><![CDATA[lamp]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[post]]></category>
		<category><![CDATA[projects]]></category>

		<guid isPermaLink="false">http://vallery.net/2007/05/17/debug-your-outbound-post-and-get-requests/</guid>
		<description><![CDATA[I work a lot with different types of web services. I find when I&#8217;m building an application that has to post data off to a remote service that it can be difficult to debug where the problems are. I can&#8217;t always see an exact copy of the HTTP request that I am sending, and therefore [...]]]></description>
		<wfw:commentRss>http://vallery.net/2007/05/17/debug-your-outbound-post-and-get-requests/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Optimizing WordPress and LAMP to survive the Digg effect</title>
		<link>http://vallery.net/2007/03/26/optimizing-wordpress-and-lamp-to-survive-the-digg-effect/</link>
		<comments>http://vallery.net/2007/03/26/optimizing-wordpress-and-lamp-to-survive-the-digg-effect/#comments</comments>
		<pubDate>Mon, 26 Mar 2007 13:40:34 +0000</pubDate>
		<dc:creator>jvallery</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[digg]]></category>
		<category><![CDATA[lamp]]></category>
		<category><![CDATA[projects]]></category>

		<guid isPermaLink="false">http://vallery.net/2007/03/26/optimizing-wordpress-and-lamp-to-survive-the-digg-effect/</guid>
		<description><![CDATA[Anyone who has used digg for any amount of time has certainly come across a dead link. Invariably you click on the comment link hoping someone has posted a mirror of the content. You head over to duggmirror or coral cache to view the content. During the peak time right after an article hits the [...]]]></description>
		<wfw:commentRss>http://vallery.net/2007/03/26/optimizing-wordpress-and-lamp-to-survive-the-digg-effect/feed/</wfw:commentRss>
		<slash:comments>28</slash:comments>
		</item>
	</channel>
</rss>

