Re: [Django] #17026: Message storage backends section missing "just use x"

[Django]

#17026: Message storage backends section missing "just use x"
-+-
 Reporter:  coolRR   |Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [ce53a1d0bf51f59118569ec81e1a30b013bd352e]:
 {{{
 #!CommitTicketReference repository=""
 revision="ce53a1d0bf51f59118569ec81e1a30b013bd352e"
 Clarified the messages documentation.

 * Stated upfront that the messages framework is enabled by default.
 * Explained why FallbackStorage, despites its unattractive name, is the
   default and likely the most efficient message storage class.

 Thanks Jeremy Dunck for the review.

 Closes #17026 (again).
 }}}

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17026: Message storage backends section missing "just use x"

[Django]

#17026: Message storage backends section missing "just use x"
-+-
 Reporter:  coolRR   |Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin
 * status:  reopened => new


-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17026: Message storage backends section missing "just use x"

[Django]

#17026: Message storage backends section missing "just use x"
--+
 Reporter:  coolRR|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * status:  closed => reopened
 * version:  1.3 => master
 * resolution:  fixed =>


Comment:

 I came across this section of the docs today (while debugging #18781) and
 thought "oh, what are the advantages and drawbacks of the three storage
 backends?".

 So... I'd like to revisit this ticket.

 The backends were introduced in [25020ddb05] as a consequence of #4604.
 The discussion on the ticket is quite long but there's a good summary on
 the SessionMessages wiki page. Notably it mentions the following
 requirement:
 > Use the session only as a fallback: Avoid database/cache queries if
 possible, but support larger messages that don't fit in a cookie (> 4kb)
 when needed

 [[BR]]

 I think the docs should say something along the lines of:
 - !FallbackStorage optimizes for the general case by using cookies for
 small messages, and the session only when messages don't fit in a cookie.
 In general, there's no reason to use anything else.
 - if your site doesn't use `django.contrib.sessions`, use !CookieStorage
 - if you have a good reason to keep your cookies minimal (hint: you
 probably don't), use !SessionStorage

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17026: Message storage backends section missing "just use x"

[Django]

#17026: Message storage backends section missing "just use x"
--+
 Reporter:  coolRR|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Claude Paroz ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [03896eb5df74a47237ec3ed9a73aadc925e90dbb]:
 {{{
 #!CommitTicketReference repository=""
 revision="03896eb5df74a47237ec3ed9a73aadc925e90dbb"
 Fixed #17026 -- Improved wording of contrib.messages' storage backends
 section
 }}}

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17026: Message storage backends section missing "just use x" (was: Docs section missing "just use x")

[Django]

#17026: Message storage backends section missing "just use x"
--+
 Reporter:  coolRR|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Indeed, this section is a bit confusing, mostly because it describes
 complex backwards-compatibility code. It could use a better structure.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.