Re: [Django] #30517: Base class for Key Value engines for caching

[Django]

#30517: Base class for Key Value engines for caching
-+-
 Reporter:  dulmandakh   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  redis| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by dulmandakh:

Old description:

> I think that it would be best to have built-in support for Redis caching
> in Django, as it's getting more popular and has other use cases than just
> caching. And I found that most of the features overlap with memcached. So
> I think that it might be better to refactor BaseMemcachedCache to be base
> for KV engines, and use it for both Memcached and Redis, to reduce code
> duplication.
>
> I can work on this if approved.

New description:

 I think that it would be best to have built-in support for Redis caching
 in Django, as it's getting more popular and has other use cases than just
 caching. And I found that most of the features overlap with memcached. So
 I think that it might be better to refactor BaseMemcachedCache to be base
 for KV engines, and use it for both Memcached and Redis, to reduce code
 duplication.

 I would like to start discussion about best approach adding Redis support
 into Django. Also I can work on this if approved.

--

-- 
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 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/068.2dda7c79c2bdf73a9168200b3e6d6101%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30517: Base class for Key Value engines for caching

[Django]

#30517: Base class for Key Value engines for caching
-+-
 Reporter:  dulmandakh   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  redis| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dulmandakh):

 * keywords:   => redis


-- 
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 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/068.36cb422450bb9e1f74fccdf231e4f802%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30517: Base class for Key Value engines for caching

[Django]

#30517: Base class for Key Value engines for caching
+
   Reporter:  dulmandakh|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Cache system)   |Version:  master
   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 |
+
 I think that it would be best to have built-in support for Redis caching
 in Django, as it's getting more popular and has other use cases than just
 caching. And I found that most of the features overlap with memcached. So
 I think that it might be better to refactor BaseMemcachedCache to be base
 for KV engines, and use it for both Memcached and Redis, to reduce code
 duplication.

 I can work on this if approved.

-- 
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 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/053.c42845fb54ab9f83d4a18c00f9fff61e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.