#20922: Allow customizing the serializer used by contrib.sessions
----------------------------------+------------------------------------
Reporter: gwahl@… | Owner: timo
Type: New feature | Status: assigned
Component: contrib.sessions | Version: 1.5
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by timo):
1. No, model instances are not serializable using JSON. Its limitations
are noted in the documentation. An application would be responsible for
serializing the instance before storing it in a session.
2. We're not planning implementing the "hook" idea.
3. N/A, we're not implementing this API.
4. As hinted to above, our design decision boiled down to "it's up to the
application to only store simple data structures in sessions." See the
changes to `contrib.messages` for an example.
5. Sessions will be dropped (the release notes for 1.6 and 1.5.3 will
mention this). `SessionBase.decode` catches deserialization exceptions and
returns an empty session.
--
Ticket URL: <https://code.djangoproject.com/ticket/20922#comment:5>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/077.20460b42248afe3e3f34f227c19c0a6f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
