Conceptual difference between a project and an application

[Spider]

Can someone explan to me the underlying concept behind the distinction
between django "projects" and "applications"?

I know that an application is part of a project, and it's many-to-many,
so an app can be part of more than one project, and a project can
contain more than one app. But what to projects and apps actually
"correspond" to? Is a project just a place to hold the url mapping
scheme? Is an app purely a logical construct, or is it envisaged that
each app handles one set of URLs?

Thanks

[Frankie Robertson]

On 04/07/06, Spider <mat...@cuneiformsoftware.com> wrote:
>
> Can someone explan to me the underlying concept behind the distinction
> between django "projects" and "applications"?
>
> I know that an application is part of a project, and it's many-to-many,
> so an app can be part of more than one project, and a project can
> contain more than one app. But what to projects and apps actually
> "correspond" to? Is a project just a place to hold the url mapping
> scheme?

Applications can hold the url mapping scheme, see the admin for an example.

> Is an app purely a logical construct, or is it envisaged that
> each app handles one set of URLs?

An application is a set of views and models, in most cases each app
will only handle one set of urls, but this is not neccesarly the case.

An intresting example would be the "tracker" application posted here
(http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Fe-scribe.com%2Fnews%2F230&ei=S6OqRJWII5KKwQHDp-nQBw&sig2=cyA_wfLKX6mXqN7ZSlcNMg)
a while ago. You can put the application in a central place and then
install it on a number of projects.

You can usually just think of a project mapping on to a domain name.

Honestly, my approach with this is just to use whatever works.

HTH,

Frankie.

>
> Thanks
>
>
> >
>