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' application, and install it into Client > A's site and Client C's site, and a 'store' application, and install > it for Client B and Client C. Because Django applications are > portable, you only have to write each application once, and then you > can install it into as many sites as you need to.
And don't forget that Client C can then log in once for both the online store and the weblog and share the same user and session data. If they were told that was not possible, they probably wouldn't like that as they don't see them as 2 separate apps, just separate parts of one. On various lists and forum's I often see questions about how two (or more) sepperate apps installed for a single client can share this data. Seeing each app is developed seperately, its not always easy or possable. Django eliminates that problem as long as all apps are developed using Django. As we begin to see some apps released into the public domain, this will really make things easy. On the other hand, if this behavior is undesirable, one could always put each app in a separate project. -- ---- Waylan Limberg [EMAIL PROTECTED]
