Re: [Django] #33760: Allow setting session cookie name dynamically

[Django]

#33760: Allow setting session cookie name dynamically
--+--
 Reporter:  Dan Strokirk  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.sessions  |  Version:  4.1
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Dan Strokirk):

 Absolutely, thanks!

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018123667221-1a295192-050d-4330-97aa-42003741d3b2-00%40eu-central-1.amazonses.com.

Re: [Django] #33760: Allow setting session cookie name dynamically

[Django]

#33760: Allow setting session cookie name dynamically
--+--
 Reporter:  Dan Strokirk  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.sessions  |  Version:  4.1
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Carlton Gibson):

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


Comment:

 Hi.

 I'd likely think this too niche to justify the additional hooks.

 Can I ask you to post to the DevelopersMailingList, which is a better
 venue for these kind of feature requests than the ticket tracker here,
 which gets far fewer eyes? If there's a general approval then we can
 reopen. Thanks.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701812313ec36-f7c146ab-8aac-4b41-85c3-79879f1684ee-00%40eu-central-1.amazonses.com.

[Django] #33760: Allow setting session cookie name dynamically

[Django]

#33760: Allow setting session cookie name dynamically
+
   Reporter:  Dan Strokirk  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  contrib.sessions  |Version:  4.1
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Currently it's only possible to use a single session cookie, but it can be
 useful in a multi-tenant application to use multiple session cookies.

 Adding a new `get_cookie_name` or `get_cookie_params` method to the
 `SessionMiddleware` class might be one way to implement this, which means
 that you can then then use your own subclassed middleware to override it.

 If this seems like a reasonable feature to add I'd be glad to supply a
 patch.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018120fbb9df-fe1158b5-874f-43d1-965f-140dd973cdf1-00%40eu-central-1.amazonses.com.