Lately I've been seeing a lot of people running into the problem of needing something resembling the auth app's message framework, but being unable to use it because they need to display messages to users who aren't associated with an auth.User instance.
It seems to me that the easiest thing to do, if I were going to roll my own solution to this problem, would be to replicate most of what auth.Message provides, but instead tie it to an instance of Session -- this way, I could reliably associate a Message with anyone who's using the site (provided, of course, that they've got cookies turned on, but that's a better requirement to cope with than needing everyone to be authenticated at all times). Which leads me to wonder whether it wouldn't be better to just do that in Django itself, and move the Message model into django.contrib.sessions. Of course, this would be a backwards-incompatible change and would require refactoring of Django and of any end-user applications which were using the messages framework (including possibly imposing a dependency on sessions where none existed before). Anyone have strong feelings one way or another? -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
