There are a couple of places in the documentation that refer to "application instances":
<https://docs.djangoproject.com/en/dev/topics/http/urls/#introduction> <https://docs.djangoproject.com/en/dev/ref/contrib/admin/#multiple-admin-sites-in-the-same-urlconf> However, it's not really clear what an application instance is or why I might need to deploy multiple instances of one. I think that's worth explaining in the documentation, especially since I have found a number of questions and discussions on the subject elsewhere. I'd suggest that the explanation be incorporated in the URLs documentation. Is the following largely correct: * an application runs as an instance * normally one doesn't need to worry about this * sometimes though one might want to run an additional instance of an application * one names the multiple instances through the "namespace" argument in a URL pattern * URL reversing is the only reason we'd have for naming the multiple instances I still don't quite see why one might want to run an additional instance of an application. If it's just to provide a different set of URLs for it, why not write some additional URLs to the views that the provide the different functionality? Daniele -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
