On Jun 20, 3:58 am, "Joseph Heck" <[EMAIL PROTECTED]> wrote: > Out of curiousity, what's the reason to try and keep them separate > instead of just layering it over the session mechanism?
Mainly due to the limitation of context processors that they can't see or change the current context. The core auth context processor pushes it's messages to the "message" context variable. It would have to be done in that same processor to be able to catch both session and auth messages and push them to the same context variable but then you can't have full sessions message functionality without using the combined processor.. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
