django-select2/django_select2/cache.py

"""
Shared memory across multiple machines to the heavy AJAX lookups.

Select2 uses django.core.cache_ to share fields across
multiple threads and even machines.

Select2 uses the cache backend defined in the setting
``SELECT2_CACHE_BACKEND`` [default=``default``].

It is advised to always setup a separate cache server for Select2.

.. _django.core.cache: https://docs.djangoproject.com/en/dev/topics/cache/
"""
from django.core.cache import caches

from .conf import settings

__all__ = ('cache', )

cache = caches[settings.SELECT2_CACHE_BACKEND]
Removed own caching solution in favour of django caching The old multiprocessing support was hard to maintain. Since signing and caching are part of `django.core` there is really no need to stick to our own solution. As a result multimachine support and security are now always in place. Fields are stored in Django's cache. The default cache used by select2 is called 'default' but can be cachanged overwriting the setting `SELECT2_CACHE_BACKEND`. Recommended cache backends are memcached, redis or a DB-cache. Refactored AutoResponseView The main reason for this refactoring is the fact that the pagingnation was slow. I dropped major parts of the initial code and wrote a more django-like-approach. Noteabley: - get_results now retuns a QuerySet - This commit drops django 1.6 support in favour of the JsonResponse (Backporting is possible). 2015-07-17 18:10:16 +00:00			`"""`
enchant the docs -- adds spell checking 2016-02-04 10:47:21 +00:00			`Shared memory across multiple machines to the heavy AJAX lookups.`
Removed own caching solution in favour of django caching The old multiprocessing support was hard to maintain. Since signing and caching are part of `django.core` there is really no need to stick to our own solution. As a result multimachine support and security are now always in place. Fields are stored in Django's cache. The default cache used by select2 is called 'default' but can be cachanged overwriting the setting `SELECT2_CACHE_BACKEND`. Recommended cache backends are memcached, redis or a DB-cache. Refactored AutoResponseView The main reason for this refactoring is the fact that the pagingnation was slow. I dropped major parts of the initial code and wrote a more django-like-approach. Noteabley: - get_results now retuns a QuerySet - This commit drops django 1.6 support in favour of the JsonResponse (Backporting is possible). 2015-07-17 18:10:16 +00:00
			`Select2 uses django.core.cache_ to share fields across`
			`multiple threads and even machines.`

enchant the docs -- adds spell checking 2016-02-04 10:47:21 +00:00			`Select2 uses the cache backend defined in the setting`
Removed own caching solution in favour of django caching The old multiprocessing support was hard to maintain. Since signing and caching are part of `django.core` there is really no need to stick to our own solution. As a result multimachine support and security are now always in place. Fields are stored in Django's cache. The default cache used by select2 is called 'default' but can be cachanged overwriting the setting `SELECT2_CACHE_BACKEND`. Recommended cache backends are memcached, redis or a DB-cache. Refactored AutoResponseView The main reason for this refactoring is the fact that the pagingnation was slow. I dropped major parts of the initial code and wrote a more django-like-approach. Noteabley: - get_results now retuns a QuerySet - This commit drops django 1.6 support in favour of the JsonResponse (Backporting is possible). 2015-07-17 18:10:16 +00:00			``SELECT2_CACHE_BACKEND`` [default=``default``].

			`It is advised to always setup a separate cache server for Select2.`

			`.. _django.core.cache: https://docs.djangoproject.com/en/dev/topics/cache/`
			`"""`
Radical removal of all unneeded code 2015-08-06 09:58:27 +00:00			`from django.core.cache import caches`
Removed own caching solution in favour of django caching The old multiprocessing support was hard to maintain. Since signing and caching are part of `django.core` there is really no need to stick to our own solution. As a result multimachine support and security are now always in place. Fields are stored in Django's cache. The default cache used by select2 is called 'default' but can be cachanged overwriting the setting `SELECT2_CACHE_BACKEND`. Recommended cache backends are memcached, redis or a DB-cache. Refactored AutoResponseView The main reason for this refactoring is the fact that the pagingnation was slow. I dropped major parts of the initial code and wrote a more django-like-approach. Noteabley: - get_results now retuns a QuerySet - This commit drops django 1.6 support in favour of the JsonResponse (Backporting is possible). 2015-07-17 18:10:16 +00:00
			`from .conf import settings`

			`__all__ = ('cache', )`

Radical removal of all unneeded code 2015-08-06 09:58:27 +00:00			`cache = caches[settings.SELECT2_CACHE_BACKEND]`