<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Zend Framework: Encapsulating routes into modules</title>
	<atom:link href="http://blog.fedecarg.com/2008/08/03/zend-framework-encapsulating-routes-into-modules/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fedecarg.com/2008/08/03/zend-framework-encapsulating-routes-into-modules/</link>
	<description>Simple is better than complex. Complex is better than complicated. &#124; @fedecarg</description>
	<lastBuildDate>Mon, 06 Feb 2012 14:38:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Federico</title>
		<link>http://blog.fedecarg.com/2008/08/03/zend-framework-encapsulating-routes-into-modules/#comment-1166</link>
		<dc:creator><![CDATA[Federico]]></dc:creator>
		<pubDate>Tue, 05 Aug 2008 01:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://phpimpact.wordpress.com/?p=485#comment-1166</guid>
		<description><![CDATA[Great news. Martel and Ben are doing an excellent job. Thanks for the update.]]></description>
		<content:encoded><![CDATA[<p>Great news. Martel and Ben are doing an excellent job. Thanks for the update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Weier O'Phinney</title>
		<link>http://blog.fedecarg.com/2008/08/03/zend-framework-encapsulating-routes-into-modules/#comment-1162</link>
		<dc:creator><![CDATA[Matthew Weier O'Phinney]]></dc:creator>
		<pubDate>Mon, 04 Aug 2008 19:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://phpimpact.wordpress.com/?p=485#comment-1162</guid>
		<description><![CDATA[Martel and Ben have introduced route chaining into trunk, and this will be the solution used for hostname based routing for 1.6. For 1.7, they plan to modify the routes to allow partial matching, which will allow you to chain several routes together to get a match. One primary use case is for localized routes, where all routes need a language string -- this would require a single route which then chains a variety of other routes. This should result in better routing performance, as well as more flexible and extendible routing solutions.]]></description>
		<content:encoded><![CDATA[<p>Martel and Ben have introduced route chaining into trunk, and this will be the solution used for hostname based routing for 1.6. For 1.7, they plan to modify the routes to allow partial matching, which will allow you to chain several routes together to get a match. One primary use case is for localized routes, where all routes need a language string &#8212; this would require a single route which then chains a variety of other routes. This should result in better routing performance, as well as more flexible and extendible routing solutions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

