<?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>Crazy&#039;s Blog &#187; PHP</title>
	<atom:link href="http://blog.crazytje.be/tag/php/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.crazytje.be</link>
	<description></description>
	<lastBuildDate>Sun, 28 Aug 2011 13:37:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Using APC to store your data</title>
		<link>http://blog.crazytje.be/using-apc-to-store-your-data/</link>
		<comments>http://blog.crazytje.be/using-apc-to-store-your-data/#comments</comments>
		<pubDate>Tue, 31 Aug 2010 15:14:56 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[APC]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[apc]]></category>
		<category><![CDATA[opcode caching]]></category>
		<category><![CDATA[optimalization]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=387</guid>
		<description><![CDATA[Sometimes you have large amount of generated data that you don’t want to create on every web request. An examples would be a home page with several news posts on it. The text would be in a database, but all the ‘extra’ things you did like bbtags present in the text, information about the user <a href='http://blog.crazytje.be/using-apc-to-store-your-data/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/using-apc-to-store-your-data/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimizing your web server: Part 4b – XDebug Profiler</title>
		<link>http://blog.crazytje.be/optimizing-your-web-server-part-4b-%e2%80%93-xdebug-profiler-2/</link>
		<comments>http://blog.crazytje.be/optimizing-your-web-server-part-4b-%e2%80%93-xdebug-profiler-2/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 20:21:08 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[optimalization]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[profile]]></category>
		<category><![CDATA[xdebug]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=297</guid>
		<description><![CDATA[Here we are, part 4b. By using XDebug, a pecl extension, our php code can be analyzed pinpointing the slower functions. Installing XDebug is easy: pecl install xdebug Now, you&#8217;ll have to enable it in the php.ini file: extension=xdebug.so xdebug.profiler_enable=1 xdebug.profiler_output_name=profiler-%s-%t.cache xdebug.profiler_output_dir=/tmp/xdebug Don&#8217;t forget to create the directory and give apache enough permissions to write <a href='http://blog.crazytje.be/optimizing-your-web-server-part-4b-%e2%80%93-xdebug-profiler-2/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/optimizing-your-web-server-part-4b-%e2%80%93-xdebug-profiler-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimizing your web server: Part 4a – PHP</title>
		<link>http://blog.crazytje.be/optimizing-your-web-server-part-4a-%e2%80%93-php/</link>
		<comments>http://blog.crazytje.be/optimizing-your-web-server-part-4a-%e2%80%93-php/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 20:15:35 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[optimalization]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=236</guid>
		<description><![CDATA[Let me start by saying, I won&#8217;t bore you with the list of what I call stupid optimizations. That&#8217;s why I call this 4a, I recommend skipping 4a and go directly to 4b When I first when on my quest to optimize my code, I was disappointed at what I found. Let me give you <a href='http://blog.crazytje.be/optimizing-your-web-server-part-4a-%e2%80%93-php/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/optimizing-your-web-server-part-4a-%e2%80%93-php/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Single Instance PHP Script</title>
		<link>http://blog.crazytje.be/single-instance-php-script/</link>
		<comments>http://blog.crazytje.be/single-instance-php-script/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 21:11:01 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[single instance]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=135</guid>
		<description><![CDATA[When using php scripts on the command line or in the cron, there are often times that you do not want to allow the same script to run more then once at a the same time. So a single instance application in php. Personally I use php scripts like this allot. My cron is filled <a href='http://blog.crazytje.be/single-instance-php-script/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/single-instance-php-script/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Changing the Session ID in CakePHP</title>
		<link>http://blog.crazytje.be/changing-the-session-id-in-cakephp/</link>
		<comments>http://blog.crazytje.be/changing-the-session-id-in-cakephp/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 20:58:52 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[CakePHP]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[components]]></category>
		<category><![CDATA[sessions]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=95</guid>
		<description><![CDATA[Ever wanted to set your own session id? Well, I did. I was creating a webservice where authentication would be done with a &#8216;token&#8217;. This token would simply be a random guid given to that user after he logged on with his username/password. Now, this random guid/string would be the session ID. That way, if <a href='http://blog.crazytje.be/changing-the-session-id-in-cakephp/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/changing-the-session-id-in-cakephp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CakePHP: Extending the AppController</title>
		<link>http://blog.crazytje.be/cakephp-extending-the-appcontroller/</link>
		<comments>http://blog.crazytje.be/cakephp-extending-the-appcontroller/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 21:17:29 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[CakePHP]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[app controller]]></category>
		<category><![CDATA[extending classes]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=90</guid>
		<description><![CDATA[Ever wanted to split off functionality to a base class other then AppController? This is what was needed to prevent typing the same code over and over again in a project of mine. The app controller is great and all, but it&#8217;s just one class and you might want some functionality in only a part <a href='http://blog.crazytje.be/cakephp-extending-the-appcontroller/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/cakephp-extending-the-appcontroller/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to add variables to APC?</title>
		<link>http://blog.crazytje.be/how-to-add-variables-to-apc/</link>
		<comments>http://blog.crazytje.be/how-to-add-variables-to-apc/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 19:52:06 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[APC]]></category>
		<category><![CDATA[apc]]></category>
		<category><![CDATA[opcode caching]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=63</guid>
		<description><![CDATA[This is as follow up on my previous blog post on &#8220;Why use an opcode cacher&#8221; In that post I mention you can store data in memory. The reason why one should want to do this, is again &#8220;performance&#8221; Just think about it, for each request, what amount of data is gotten over and over <a href='http://blog.crazytje.be/how-to-add-variables-to-apc/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/how-to-add-variables-to-apc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP Opcode caching: Why use an opcode cacher?</title>
		<link>http://blog.crazytje.be/php-opcode-caching-why-use-an-opcode-cacher/</link>
		<comments>http://blog.crazytje.be/php-opcode-caching-why-use-an-opcode-cacher/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 17:12:09 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[APC]]></category>
		<category><![CDATA[Operations]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[apc]]></category>
		<category><![CDATA[eaccelerator]]></category>
		<category><![CDATA[opcode caching]]></category>
		<category><![CDATA[xcache]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=45</guid>
		<description><![CDATA[Why use an opcode cacher? When users surf to the website(s) hosted on your machine, the php files are compiled each time. Compiling the php code you worked so hard to develop takes time, and the more files you have, the longer it takes. This is especially the case when using PHP frameworks(personally I use <a href='http://blog.crazytje.be/php-opcode-caching-why-use-an-opcode-cacher/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/php-opcode-caching-why-use-an-opcode-cacher/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Parse CDATA with SimpleXML</title>
		<link>http://blog.crazytje.be/parse-cdata-with-simplexml/</link>
		<comments>http://blog.crazytje.be/parse-cdata-with-simplexml/#comments</comments>
		<pubDate>Sat, 17 Oct 2009 18:21:28 +0000</pubDate>
		<dc:creator>Crazy</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[cdata]]></category>
		<category><![CDATA[simplexml]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://blog.crazytje.be/?p=7</guid>
		<description><![CDATA[When trying to parse xml with php&#8217;s SimpleXml you&#8217;ll notice that the SimpleXmlElement comes up empty. Say you have the following xml structure: &#60;root&#62; &#60;username&#62; &#60;![CDATA[ Text you want to escape goes here... ]]&#62; &#60;/username&#62; &#60;/root&#62; When parsing that with SimpleXml the end result will simply be an empty tag: &#60;root&#62; &#60;username&#62; &#60;/username&#62; &#60;/root&#62; To <a href='http://blog.crazytje.be/parse-cdata-with-simplexml/'>[...]</a>]]></description>
		<wfw:commentRss>http://blog.crazytje.be/parse-cdata-with-simplexml/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

