Any ideas? Any suggestions?

On Sat, Jul 12, 2008 at 9:11 PM, AmirBehzad Eslami <[EMAIL PROTECTED]>
wrote:

> Hi,
>
> Suppose that you're designing a simple website to
> allow people to upload photos. There are two major
> entities here: Users and Photos. Each user has "0 to n" photos.
>
> From a modular perspective, you can develop two modules:
> Users, and Photos.
>
> The module Users contains some Action-Controllers for registration,
> authentication, change password, remind password, edit profile, etc.
> and the module Photos is responsible for displaying photos, search for
> photos, etc.
>
> However, there are a few tasks that their functionality is not limited to a
> single
> module.
> 1) A user wants to upload a photo
> 2) Display a user's photos
>
> Where do you put the action controller for this tasks?
> In the Users module, or in the Photos module? or in a new module?
>
> Is there any design principle to help the developers to decide where
> to put the action-controllers in different modules? What are your
> experiences?
>
> Kind regards,
> -abe




-- 
Kind regards,
-behzad

Reply via email to