On 6/19/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> Keep in mind how get_and_delete_messages() currently works; it
> retrieves the messages and removes them so they won't show up on
> subsequent page views. There would need to be some mechanism to
> achieve this, so it would have to be something
On Jun 20, 5:27 am, "Amit Upadhyay" <[EMAIL PROTECTED]> wrote:
> On 6/19/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > I'd be +1 on just switching the whole thing (messages for all users,
> > authenticated or not) to using sessions, in which case
> > django.contrib.auth.models.Message should be
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 co
On 6/19/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> Why is request.session["_messages"] not enough? It can be a list of string
> messages.
Keep in mind how get_and_delete_messages() currently works; it
retrieves the messages and removes them so they won't show up on
subsequent page views. Ther
On 6/19/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> I'd be +1 on just switching the whole thing (messages for all users,
> authenticated or not) to using sessions, in which case
> django.contrib.auth.models.Message should be deprecated and replaced
> by django.contrib.sessions.models.Message.
On 6/19/07, 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?
I'd be +1 on just switching the whole thing (messages for all users,
authenticated or not) to using sessions, in which
Out of curiousity, what's the reason to try and keep them separate
instead of just layering it over the session mechanism?
-joe
On 6/18/07, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> It's not difficult for someone to implement this themselves, but it
> does seem useful enough (imo) for core.
>
>
It's not difficult for someone to implement this themselves, but it
does seem useful enough (imo) for core.
I have also contributed a patch to that ticket (sorry for the hijack)
with docs and tests, calling the framework "visitor messages" to keep
it separate from auth's "messages" framework.
-
I created a ticket for a new way of passing messages and the first response
said that I should bring it up to the dev group for a design decision.
http://code.djangoproject.com/ticket/4604 - that's the ticket (with patch).
Basically, it stores messages according to session rather than according t
