<?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: Zend Framework custom URLs</title>
	<atom:link href="/2009/10/27/zend-framework-custom-urls/feed/" rel="self" type="application/rss+xml" />
	<link>/2009/10/27/zend-framework-custom-urls/</link>
	<description>on web development</description>
	<lastBuildDate>Fri, 26 Oct 2018 21:40:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.0.3</generator>
	<item>
		<title>By: Jaskaran Singh</title>
		<link>/2009/10/27/zend-framework-custom-urls/comment-page-1/#comment-340059</link>
		<dc:creator><![CDATA[Jaskaran Singh]]></dc:creator>
		<pubDate>Thu, 16 Jul 2015 05:08:49 +0000</pubDate>
		<guid isPermaLink="false">/?p=769#comment-340059</guid>
		<description><![CDATA[Nice tutorial, I was struggling to achive such functionality since long, Worked for me!

Thanks!!!]]></description>
		<content:encoded><![CDATA[<p>Nice tutorial, I was struggling to achive such functionality since long, Worked for me!</p>
<p>Thanks!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arvind</title>
		<link>/2009/10/27/zend-framework-custom-urls/comment-page-1/#comment-19393</link>
		<dc:creator><![CDATA[Arvind]]></dc:creator>
		<pubDate>Thu, 26 Sep 2013 06:21:51 +0000</pubDate>
		<guid isPermaLink="false">/?p=769#comment-19393</guid>
		<description><![CDATA[Nice tutorial 

Keep writing 

Thanks,]]></description>
		<content:encoded><![CDATA[<p>Nice tutorial </p>
<p>Keep writing </p>
<p>Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seb</title>
		<link>/2009/10/27/zend-framework-custom-urls/comment-page-1/#comment-9619</link>
		<dc:creator><![CDATA[Seb]]></dc:creator>
		<pubDate>Sat, 28 Nov 2009 18:42:45 +0000</pubDate>
		<guid isPermaLink="false">/?p=769#comment-9619</guid>
		<description><![CDATA[Hi Guys,

Great tips!
One question I&#039;d have - we have the control panel for our custom cms which allows administrator to define keywords for each page - say you have page about_us - and administrator can also define the keyword which is displayed before the page name. Is there a way to achieve it using ZF?
I believe that the path to each page (controller) would be generated dynamically depending on the value stored in the database.

Any ideas how to accomplished this?]]></description>
		<content:encoded><![CDATA[<p>Hi Guys,</p>
<p>Great tips!<br />
One question I&#8217;d have &#8211; we have the control panel for our custom cms which allows administrator to define keywords for each page &#8211; say you have page about_us &#8211; and administrator can also define the keyword which is displayed before the page name. Is there a way to achieve it using ZF?<br />
I believe that the path to each page (controller) would be generated dynamically depending on the value stored in the database.</p>
<p>Any ideas how to accomplished this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stoimen</title>
		<link>/2009/10/27/zend-framework-custom-urls/comment-page-1/#comment-7264</link>
		<dc:creator><![CDATA[Stoimen]]></dc:creator>
		<pubDate>Wed, 28 Oct 2009 12:25:27 +0000</pubDate>
		<guid isPermaLink="false">/?p=769#comment-7264</guid>
		<description><![CDATA[Thanks for the advice! I really appreciate your recommendation which indeed defines more structured way to implement custom routes in ZF. The solution I described doesn&#039;t pretend to be the best one, but simply another working solution. I agree it is more patch-like.

I&#039;d like to post another article based on the way you described. 

Thank you again!]]></description>
		<content:encoded><![CDATA[<p>Thanks for the advice! I really appreciate your recommendation which indeed defines more structured way to implement custom routes in ZF. The solution I described doesn&#8217;t pretend to be the best one, but simply another working solution. I agree it is more patch-like.</p>
<p>I&#8217;d like to post another article based on the way you described. </p>
<p>Thank you again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Weier O'Phinney</title>
		<link>/2009/10/27/zend-framework-custom-urls/comment-page-1/#comment-7262</link>
		<dc:creator><![CDATA[Matthew Weier O'Phinney]]></dc:creator>
		<pubDate>Wed, 28 Oct 2009 12:06:56 +0000</pubDate>
		<guid isPermaLink="false">/?p=769#comment-7262</guid>
		<description><![CDATA[There&#039;s a much easier way to create shorter, more targetted URLs: create custom routes.

Zend Framework provides several types of custom routes you can attach to the router, as well as an interface you can utilize to create your own. The standard routes include: &quot;Route&quot;, which allows you to create routes with identified placeholder segments (think: &quot;blog/:year/:month/:day&quot;); &quot;Static&quot;, for routes with no dynamic segments; &quot;Regex&quot;, for using regular expressions to split the route; and &quot;Rest&quot;, for defining routes that adhere to RESTful principles. The route interface simply asks for you to define match() and assemble() methods, which allows you to define any functionality you want.

I highly recommend this approach over what you have blogged.]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s a much easier way to create shorter, more targetted URLs: create custom routes.</p>
<p>Zend Framework provides several types of custom routes you can attach to the router, as well as an interface you can utilize to create your own. The standard routes include: &#8220;Route&#8221;, which allows you to create routes with identified placeholder segments (think: &#8220;blog/:year/:month/:day&#8221;); &#8220;Static&#8221;, for routes with no dynamic segments; &#8220;Regex&#8221;, for using regular expressions to split the route; and &#8220;Rest&#8221;, for defining routes that adhere to RESTful principles. The route interface simply asks for you to define match() and assemble() methods, which allows you to define any functionality you want.</p>
<p>I highly recommend this approach over what you have blogged.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
