On 2/21/06, iGL <[EMAIL PROTECTED]> wrote: > > Hi, > As I suppose, the Django's concept of separation of application from > a project, when several apps form the latter, is a very nice > abstraction of the traditional MVC. It would enable one to re-use apps > in an extent exceeding what is provided with the "classic" MVC. > > However, to do so, one has to organize the model of an app in such a > way that the app mustn't know anything (or, more precisely, as few as > needed) about its "neighbors". > > That's my question: is there a documentation, or informal blog > postings, describing how different apps can share data via > django.core.Site? Browsing django.contrib source is a good way, but the > aforementioned (docs, blog postings) would also help.
Using Site is the same as using any other external model module; once you import it, you can refer to parts of it (e.g., through ForeignKeys) just like parts defined in your local model module. Site isn't "special" in this respect. :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
