Thanks Everyone for your input.
Regards,
Armin
On 12/21/05, Armin <[EMAIL PROTECTED]> wrote:
> Thanks James for the great example. So, online store which is a huge
> project all by itself will not be broken down to multiple apps? But
> will be used as a simple package.
If it would be easier to maintain as one application, do it as one
applica
On 12/21/05, James Bennett <[EMAIL PROTECTED]> wrote:
>
> Client A is an individual who wants to have a weblog.
>
> Client B is a company that wants to have an online store.
>
> Client C is a company that wants to have both an online store and a weblog.
>
> So you could write a 'weblog' applicatio
Thanks James for the great example. So, online store which is a huge
project all by itself will not be broken down to multiple apps? But
will be used as a simple package.
Armin
On 12/21/05, Armin <[EMAIL PROTECTED]> wrote:
> I don't quite understand the need for multiple 'apps'. They share the
> same 'session' variables... so you wouldn't run 2 different websites as
> two different apps. Basically, I want to get some examples of
> situations I'd need to use apps.
You do
Sorry... i typed that in a pda; a painful process indeed.
I don't quite understand the need for multiple 'apps'. They share the
same 'session' variables... so you wouldn't run 2 different websites as
two different apps. Basically, I want to get some examples of
situations I'd need to use apps.
Perhaps it is just me, but I have a bit of difficulty understanding
what you are trying to ask here. Could you please rephrase it?
Thanks,
--
Jeroen Ruigrok van der Werven
hi,
I don't think I am giving apps in django the credit they deserve.
my initial understanding of apps was that I can have 10 websites on the
same server. I recently noticed that the session is shared between
apps, and essentially I can access any model within any app. So, the
idea is for a large
8 matches
Mail list logo
