request を受け取り、response. を返すビューは、呼び出し可能です。Djangoは、ビューを関数としてのみではなく、いくつかのクラスの例を提供します。これらのクラスはあなたがビューを構造化し、継承とミックスインを利用して、コードを再利用することを可能にします。後に行うことになる単純な作業のための汎用ビューもいくつかありますが、ユースケースに合った再利用可能なビューの構造を設計したいですよね。完全な詳細に関しては class-based views reference documentation を参照してください。
\nDjango provides base view classes which will suit a wide range of applications.\nAll views inherit from the View class, which\nhandles linking the view in to the URLs, HTTP method dispatching and other\nsimple features. RedirectView is for a\nsimple HTTP redirect, and TemplateView\nextends the base class to make it also render a template.
The simplest way to use generic views is to create them directly in your\nURLconf. If you're only changing a few simple attributes on a class-based view,\nyou can simply pass them into the\nas_view() method call itself:
from django.conf.urls import url\nfrom django.views.generic import TemplateView\n\nurlpatterns = [\n url(r'^about/$', TemplateView.as_view(template_name="about.html")),\n]\nAny arguments passed to as_view() will\noverride attributes set on the class. In this example, we set template_name\non the TemplateView. A similar overriding pattern can be used for the\nurl attribute on RedirectView.
The second, more powerful way to use generic views is to inherit from an\nexisting view and override attributes (such as the template_name) or\nmethods (such as get_context_data) in your subclass to provide new values\nor methods. Consider, for example, a view that just displays one template,\nabout.html. Django has a generic view to do this -\nTemplateView - so we can just subclass it,\nand override the template name:
# some_app/views.py\nfrom django.views.generic import TemplateView\n\nclass AboutView(TemplateView):\n template_name = "about.html"\nThen we just need to add this new view into our URLconf.\nTemplateView is a class, not a function,\nso we point the URL to the as_view()\nclass method instead, which provides a function-like entry to class-based\nviews:
# urls.py\nfrom django.conf.urls import url\nfrom some_app.views import AboutView\n\nurlpatterns = [\n url(r'^about/$', AboutView.as_view()),\n]\nFor more information on how to use the built in generic views, consult the next\ntopic on generic class-based views.
\nSuppose somebody wants to access our book library over HTTP using the views\nas an API. The API client would connect every now and then and download book\ndata for the books published since last visit. But if no new books appeared\nsince then, it is a waste of CPU time and bandwidth to fetch the books from the\ndatabase, render a full response and send it to the client. It might be\npreferable to ask the API when the most recent book was published.
\nWe map the URL to book list view in the URLconf:
\nfrom django.conf.urls import url\nfrom books.views import BookListView\n\nurlpatterns = [\n url(r'^books/$', BookListView.as_view()),\n]\nAnd the view:
\nfrom django.http import HttpResponse\nfrom django.views.generic import ListView\nfrom books.models import Book\n\nclass BookListView(ListView):\n model = Book\n\n def head(self, *args, **kwargs):\n last_book = self.get_queryset().latest('publication_date')\n response = HttpResponse('')\n # RFC 1123 date format\n response['Last-Modified'] = last_book.publication_date.strftime('%a, %d %b %Y %H:%M:%S GMT')\n return response\nIf the view is accessed from a GET request, a plain-and-simple object\nlist is returned in the response (using book_list.html template). But if\nthe client issues a HEAD request, the response has an empty body and\nthe Last-Modified header indicates when the most recent book was published.\nBased on this information, the client may or may not download the full object\nlist.