<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Zendcasts Forum - Architecture (?) guestion]]></title>
		<link>http://www.zendcasts.com/forum/topic/154/architecture-guestion/</link>
		<description><![CDATA[The most recent posts in Architecture (?) guestion.]]></description>
		<lastBuildDate>Wed, 10 Mar 2010 16:06:38 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Architecture (?) guestion]]></title>
			<link>http://www.zendcasts.com/forum/post/714/#p714</link>
			<description><![CDATA[<p>modules provide another way of delineating structure in your code. If you only have 1 or 2 controller&#039;s per module, you might be over-architecting your application. They aren&#039;t required for all applications. As your application grows over time, moving over to a modular structure isn&#039;t all that difficult.</p>]]></description>
			<author><![CDATA[dummy@example.com (Jon Lebensold)]]></author>
			<pubDate>Wed, 10 Mar 2010 16:06:38 +0000</pubDate>
			<guid>http://www.zendcasts.com/forum/post/714/#p714</guid>
		</item>
		<item>
			<title><![CDATA[Architecture (?) guestion]]></title>
			<link>http://www.zendcasts.com/forum/post/711/#p711</link>
			<description><![CDATA[<p>Hello,</p><p>I was thinking if it is a good thing to put all in modules. I mean that for example if I put stuff, like logins and user management to user module, article management to article module and so on, even if there&#039;s only few or only one controller etc in a module. That way I can keep things organized. Now I have many different kinds of controllers in my default module.</p><p>What pros and cons there are doing things this way?</p>]]></description>
			<author><![CDATA[dummy@example.com (miika)]]></author>
			<pubDate>Tue, 09 Mar 2010 16:18:01 +0000</pubDate>
			<guid>http://www.zendcasts.com/forum/post/711/#p711</guid>
		</item>
	</channel>
</rss>
