James Bennett wrote: > 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
We could maintain compatibility to some extent by replacing User.messages with some bridge object with interface similar to RelatedManager (create, add, __set__ etc.) that would delegate its calls to the new session-based messages app. > (including possibly imposing a > dependency on sessions where none existed before). Authentication already somewhat depends on sessions (unless one uses custom auth middleware). And this is dependency is anyway rather weak because sessions app is light and fits almost everyone. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
