I've added the admin app, along with necessary middleware. The sessions and authentication middleware required for admin are not needed for the main part of my site, so the vast majority of traffic will be given session identifiers etc that are never used.
I haven't benchmarked in detail, but it seems sensible to separate into two different sites using the same database. I'd have one settings file with all the overhead required for the admin part, plus a lightweight version without it. The sites would run in separate mod_python instances (or whatever - I'm sure I can play around with that). Has anyone else tried this approach, or is there something better? Maybe a way to wrap the middleware to exclude it in most cases, etc? On the other hand, I can imagine having separate sites will bring about other problems... Thanks in advance for any advice. Dan --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
