On Thu, Oct 15, 2009 at 9:01 PM, wiswaud <wisw...@gmail.com> wrote: > > If i'm not mistaken, RequestContext, through context_processors.auth, > will call request.user.get_and_delete_messages() and put in the > messages to the user in the context. That's fine and dandy, except > that in most modern applications, you have client-side code that will > be calling server-side partial templates; for example, to refresh the > contents of a message div. If you use RequestContext in such views, > you'll lose the messages, unless you make sure to somehow send those > back to the client as well, and have client-side code that checks for > that.
It's strange you should raise that issue, because as of about 24 hours ago, it isn't the case any more. Luke Plant checked in some changes to trunk that make the retrieval of messages by RequestContext both lazy and memoized, so they won't be retrieved unless you explicitly request them, and they will be preserved for the length of the request once retrieved. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
