<?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>Tinsology &#187; PHP</title>
	<atom:link href="http://tinsology.net/tag/php/feed/" rel="self" type="application/rss+xml" />
	<link>http://tinsology.net</link>
	<description>Read Me</description>
	<lastBuildDate>Fri, 27 Aug 2010 08:46:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Client Side Vs. Server Side Code</title>
		<link>http://tinsology.net/2009/06/client-side-vs-server-side-code/</link>
		<comments>http://tinsology.net/2009/06/client-side-vs-server-side-code/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 19:11:31 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[(X)HTML/CSS/CMS]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=771</guid>
		<description><![CDATA[In my experience, one of the most common pitfalls for beginning programmers is not understanding the relationships between objects in their environment. This is especially the case in web development where there is in almost every case a blend between multiple client side and server side scripts. Failure to understand the the way browsers and servers communicate or the relationships between (X)HTML (or javascript or CSS etc) and PHP (insert alternative language here) will certainly lead to a poor or incorrect implementation. If you are an experienced programmer you probably won't gain much from reading this, but if you are a beginner, hopefully I can provide some insight that will save you a lot of trouble. <a href="http://tinsology.net/2009/06/client-side-vs-server-side-code/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/' rel='bookmark' title='Permanent Link: Configuring WP for Code Examples and Execution'>Configuring WP for Code Examples and Execution</a></li>
<li><a href='http://tinsology.net/2009/03/will-code-for-food/' rel='bookmark' title='Permanent Link: Will Code For Food'>Will Code For Food</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/06/client-side-vs-server-side-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PDO&#8230; Use It</title>
		<link>http://tinsology.net/2009/04/pdo-use-it/</link>
		<comments>http://tinsology.net/2009/04/pdo-use-it/#comments</comments>
		<pubDate>Sun, 05 Apr 2009 03:17:25 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PDO]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=170</guid>
		<description><![CDATA[The majority of PHP code I see, whether it be posted by a beginner on a forum, or built into a large application, seems to suggest that the current standard when accessing a database is to make use of whatever database specific commands PHP provides for your particular database (ie mysql_query, mssql_query, etc). Often times, calls to these function are coupled with various attempts to prevent sql injections (such as calls to mysql_real_escape_string). Altogether, however, to me it seems clumsy and insecure. <a href="http://tinsology.net/2009/04/pdo-use-it/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/04/validating-user-input/' rel='bookmark' title='Permanent Link: Validating User Input'>Validating User Input</a></li>
<li><a href='http://tinsology.net/2009/07/metadata/' rel='bookmark' title='Permanent Link: Metadata'>Metadata</a></li>
<li><a href='http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/' rel='bookmark' title='Permanent Link: Creating a Secure Login System the Right Way'>Creating a Secure Login System the Right Way</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/04/pdo-use-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Consolidating Error Pages with .htaccess</title>
		<link>http://tinsology.net/2009/03/consolidating-error-pages-with-htaccess/</link>
		<comments>http://tinsology.net/2009/03/consolidating-error-pages-with-htaccess/#comments</comments>
		<pubDate>Sat, 21 Mar 2009 06:24:54 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[.htaccess]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=224</guid>
		<description><![CDATA[Before I get into the topic of how to consolidate all of your error pages, let me first explain how to use .htaccess to create custom error pages. If you already know how to do this feel free to skip to the next section. <a href="http://tinsology.net/2009/03/consolidating-error-pages-with-htaccess/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/04/php-error-handling/' rel='bookmark' title='Permanent Link: PHP Error Handling'>PHP Error Handling</a></li>
<li><a href='http://tinsology.net/2009/04/wordpress-xhtml-validation/' rel='bookmark' title='Permanent Link: WordPress XHTML Validation'>WordPress XHTML Validation</a></li>
<li><a href='http://tinsology.net/2009/06/client-side-vs-server-side-code/' rel='bookmark' title='Permanent Link: Client Side Vs. Server Side Code'>Client Side Vs. Server Side Code</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/03/consolidating-error-pages-with-htaccess/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t Fear the Re(cursion)aper</title>
		<link>http://tinsology.net/2009/01/dont-fear-the-recursionaper/</link>
		<comments>http://tinsology.net/2009/01/dont-fear-the-recursionaper/#comments</comments>
		<pubDate>Sun, 18 Jan 2009 10:22:51 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Loops]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Recursion]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=102</guid>
		<description><![CDATA[For some reason whenever I see someone post code that cycles through an array or does something repeatedly, that code takes the form of some kind of loop. I admit that I'm guilty of this as well, but when I think about why I cannot come up with a reason. <a href="http://tinsology.net/2009/01/dont-fear-the-recursionaper/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/12/php-iterators/' rel='bookmark' title='Permanent Link: PHP Iterators'>PHP Iterators</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/01/dont-fear-the-recursionaper/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Intercepting Email with PHP</title>
		<link>http://tinsology.net/2009/01/intercepting-email-with-php/</link>
		<comments>http://tinsology.net/2009/01/intercepting-email-with-php/#comments</comments>
		<pubDate>Sun, 18 Jan 2009 08:21:18 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[email]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=95</guid>
		<description><![CDATA[<p>One of the most frequent questions I'm asked, or I see asked on forums is "how do I send out an email using PHP?" The answer to that is fairly simple and well documented. It more or less involves the use of a single function <a href="http://us2.php.net/function.mail">mail()</a>.</p>
<p>Something a bit more complicated and, I think, more interesting is how you can intercept an incoming email.</p> <a href="http://tinsology.net/2009/01/intercepting-email-with-php/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/04/accessing-email-through-imap-using-php/' rel='bookmark' title='Permanent Link: Accessing Email through IMAP using PHP'>Accessing Email through IMAP using PHP</a></li>
<li><a href='http://tinsology.net/2009/03/consolidating-error-pages-with-htaccess/' rel='bookmark' title='Permanent Link: Consolidating Error Pages with .htaccess'>Consolidating Error Pages with .htaccess</a></li>
<li><a href='http://tinsology.net/2010/02/php-confirmation-emails/' rel='bookmark' title='Permanent Link: PHP Confirmation Emails'>PHP Confirmation Emails</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/01/intercepting-email-with-php/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Configuring WP for Code Examples and Execution</title>
		<link>http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/</link>
		<comments>http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/#comments</comments>
		<pubDate>Wed, 14 Jan 2009 07:15:14 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[Display Code]]></category>
		<category><![CDATA[Execute PHP]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=30</guid>
		<description><![CDATA[Since launching this blog a few days ago I have yet to post and code examples or tutorials. In preperation for this, and having decided that plain text code examples just wouldn't cut it, I went searching for a plugin to format and highlight my code. Not too long afterward I came across the <a href="http://wordpress.org/extend/plugins/syntaxhighlighter/" target="_blank">SyntaxHighlighter</a> plugin. After a simple installation I was able to do things like this: <a href="http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/06/php-complex-variables-in-strings/' rel='bookmark' title='Permanent Link: PHP: Complex Variables in Strings'>PHP: Complex Variables in Strings</a></li>
<li><a href='http://tinsology.net/2009/05/inheriting-code/' rel='bookmark' title='Permanent Link: Inheriting Code'>Inheriting Code</a></li>
<li><a href='http://tinsology.net/2009/06/client-side-vs-server-side-code/' rel='bookmark' title='Permanent Link: Client Side Vs. Server Side Code'>Client Side Vs. Server Side Code</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/01/configuring-wp-for-code-examples-and-execution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
