<?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>JimmyLi.net &#187; cms</title>
	<atom:link href="http://jimmyli.net/tag/cms/feed/" rel="self" type="application/rss+xml" />
	<link>http://jimmyli.net</link>
	<description>Join the dark side</description>
	<lastBuildDate>Wed, 08 Sep 2010 07:41:53 +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>Kohana PHP Framework</title>
		<link>http://jimmyli.net/2009/02/kohana-php-framework/</link>
		<comments>http://jimmyli.net/2009/02/kohana-php-framework/#comments</comments>
		<pubDate>Wed, 25 Feb 2009 07:40:00 +0000</pubDate>
		<dc:creator>Jimmy</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[cms]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[mvc]]></category>

		<guid isPermaLink="false">http://jimmyli.net/?p=19</guid>
		<description><![CDATA[I was just reading this blog entry and it reminds me of why using a framework gives the developer so much more flexibility and better off long term, especially for business information systems where business rules change will be made.  Although comparing using a framework as opposed to an out-of-the-box solution is fairly subjective, I [...]]]></description>
			<content:encoded><![CDATA[<p>I was just reading <a href="http://sunlightlabs.com/blog/2009/02/23/content-management-systems-just-dont-work/" target="_blank">this blog entry</a> and it reminds me of why using a framework gives the developer so much more flexibility and better off long term, especially for business information systems where business rules change will be made.  Although comparing using a framework as opposed to an out-of-the-box solution is fairly subjective, I do believe that using a CMS does have its advantage when budget is tight.  However, as a full-time web developer for a company, like myself, using a framework is definitely the way to go.</p>
<p>One framework I&#8217;ve began using recently is the <a title="Kohana" href="http://kohanaphp.com" target="_blank">Kohana</a> PHP 5 Framework.  It&#8217;s a very lightweight framework using the Model-View-Controller (MVC) pattern.  While working with the framework, I&#8217;ve found several things that I really liked over several CMS software such as <a title="Joomla!" href="http://www.joomla.org" target="_blank">Joomla!</a> and <a title="Drupal" href="http://drupal.org" target="_blank">Drupal</a> could not provide (or not that I&#8217;ve noticed, at least).  I really like Kohana&#8217;s simple ability to allow all your scripts to sit under the public root, and be the core of several applications.</p>
<p>Security-wise, I like how simply it is to keep everything under the public root.  The only thing that sits on the public root is in index.php file and any client files (images, CSS, Javascript, etc.)  If the PHP parser fails and the PHP code is exposed, only the index.php is exposed to the public, and it doesn&#8217;t contain anything critical except relative paths to your main application directory, which is inaccessable publically.  Kohana has a core &#8220;system&#8221; directory, and one more or &#8220;application&#8221; directories for each of your web application.  With this type of filesystem, they&#8217;ve implemented the so-called &#8220;cascading filesystem.&#8221;  If there is anything not set in your application directory (e.g. configurations, error pages), Kohana automatically aquires those lower in the filesystem chain, with the &#8220;system&#8221; directory being at the very bottom.</p>
<p>Kohana provides all the abstraction libraries for common use functions, like database access, session management, caching, etc.  Additional modules also such as the Auth module for user authentication makes it simple to create and manage secure passwords and sessions.  Even without a URL rewrite module on your web server, building SEO-link friendly apps should not be an issue.</p>
<p>PHP itself is a very lax scripting language that lets developers do whatever they want, which can have major disadvantages when trying to create organized apps.  Having a framework like Kohana definitely helps keep many things organized.</p>
]]></content:encoded>
			<wfw:commentRss>http://jimmyli.net/2009/02/kohana-php-framework/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
