#4604: Message Passing For Anonymous Users
--------------------------------------------------------------+-------------
Reporter: Sean Patrick Hogan <[EMAIL PROTECTED]> | Owner:
SmileyChris
Status: new | Milestone:
post-1.0
Component: Contrib apps | Version:
SVN
Resolution: | Keywords:
Stage: Ready for checkin | Has_patch:
1
Needs_docs: 0 | Needs_tests:
0
Needs_better_patch: 0 |
--------------------------------------------------------------+-------------
Comment (by tobias):
To me it makes no sense to store messages with a short lifetime in
user.message_set. user.message_set should be reserved for system or
administrator messages to the user. The session is the right place to
store feedback about the current session for the user.
What if, for example, the same user is logged in from two different
browsers and completing two different tasks, simultaneously? When using
user.message_set to store feedback for the user, the messages will be
distributed on a first come first served basis, with no regard for what
session actually generated what feedback. It's bad to get in the habit of
using user.message_set for messages like "Article updated successfully,"
or other messages that really have no context outside the current session.
For these reasons, I think this patch erroneously conflates user messages
and session messages.
--
Ticket URL: <http://code.djangoproject.com/ticket/4604#comment:56>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
