<?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/"
		>
<channel>
	<title>Comments on: Re-Routeing the Zend Framework</title>
	<atom:link href="http://jeffreysambells.com/posts/2006/04/03/re-routeing-the-zend-framework/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeffreysambells.com/posts/2006/04/03/re-routeing-the-zend-framework/</link>
	<description>Geek out AFK with Jeffrey Sambells</description>
	<lastBuildDate>Thu, 11 Feb 2010 20:48:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Purvis</title>
		<link>http://jeffreysambells.com/posts/2006/04/03/re-routeing-the-zend-framework/comment-page-1/#comment-9</link>
		<dc:creator>Mike Purvis</dc:creator>
		<pubDate>Tue, 04 Apr 2006 04:34:05 +0000</pubDate>
		<guid isPermaLink="false">http://jeffreysambells.com/posts/2006/04/03/re-routeing-the-zend-framework/#comment-9</guid>
		<description>&lt;p&gt;Under the philosophy of &lt;em&gt;smart defaults&lt;/em&gt;, Rails falls back on /controller/action/id, but it also provides a routing.rb file which pretty much lets you make &#039;em look like whatever you like.&lt;/p&gt;

&lt;p&gt;Which accomplishes your stated goal of a) installing the same widget in multiple places or b) in a nested subdirectory.&lt;/p&gt;

&lt;p&gt;It sounds like Zend is following the RoR model pretty closely, so the best long-term solution is probably just to wait for their implementation of the URL mapping features. (which you say is forthcoming...)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Under the philosophy of <em>smart defaults</em>, Rails falls back on /controller/action/id, but it also provides a routing.rb file which pretty much lets you make &#8216;em look like whatever you like.</p>
<p>Which accomplishes your stated goal of a) installing the same widget in multiple places or b) in a nested subdirectory.</p>
<p>It sounds like Zend is following the RoR model pretty closely, so the best long-term solution is probably just to wait for their implementation of the URL mapping features. (which you say is forthcoming&#8230;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
