#22247: Shouldn't it say "Downstream Caches" instead of "Upstream Caches"?
-------------------------------+--------------------
Reporter: valgarv@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
[https://docs.djangoproject.com/en/1.6/topics/cache/#upstream-caches This
section in the document on Django's cache framework] mentions that, in
addition to the caching provided by Django, other cache systems exist
between the user and one's server that may intercept the request; ISP and
browser caches are given as examples. From the point of view of the
Django-based backend, all those caches are located ''downstream'' (i.e.,
in the direction from server to client). The document, however, refers to
them as "upstream".
From the client's point of view, they would indeed be "upstream"—but then
again, so would the Django cache :)
For comparison, here is
[https://developers.google.com/speed/pagespeed/module/downstream-caching
an example of usage of "downstream cache"].
--
Ticket URL: <https://code.djangoproject.com/ticket/22247>
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/058.d11f41bfe79a6466d10cf5475da1f4d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
