A view is a callable which takes a request and returns a\nresponse. This can be more than just a function, and Django provides\nan example of some classes which can be used as views. These allow you\nto structure your views and reuse code by harnessing inheritance and\nmixins. There are also some generic views for tasks which we’ll get to later,\nbut you may want to design your own structure of reusable views which suits\nyour use case. For full details, see the class-based views reference\ndocumentation.
\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 into the URLs, HTTP method dispatching and other\ncommon features. RedirectView provides a\nHTTP redirect, and TemplateView extends the\nbase class to make it also render a template.
The most direct way to use generic views is to create them directly in your\nURLconf. If you’re only changing a few attributes on a class-based view, you\ncan pass them into the as_view() method\ncall itself:
from django.urls import path\nfrom django.views.generic import TemplateView\n\nurlpatterns = [\n path('about/', TemplateView.as_view(template_name="about.html")),\n]\n as_view() 에 전달한 인자는 클래스의 속성(attributes)을 오버라이드(override)합니다. 이 예제에서는 TemplateView``에 ``template_name 을 설정합니다. 마찬가지로 url 속성(attirubte) 오버랑이딩 패턴을 :class:`~django.views.generic.base.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 subclass it, and\noverride the template name:
# some_app/views.py\nfrom django.views.generic import TemplateView\n\nclass AboutView(TemplateView):\n template_name = "about.html"\nThen we need to add this new view into our URLconf.\nTemplateView is a class, not a function, so\nwe point the URL to the as_view() class\nmethod instead, which provides a function-like entry to class-based views:
# urls.py\nfrom django.urls import path\nfrom some_app.views import AboutView\n\nurlpatterns = [\n path('about/', AboutView.as_view()),\n]\n내장 제너릭 뷰의 사용법에 대한 자세한 내용은, 다음 토픽 :doc:`generic class-based views</topics/class-based-views/generic-display>`를 참조하세요.
\n누군가 뷰를 API로 사용하여 HTTP를 통해 도서 라이브러리에 접근을 시도할 경우를 생각해 봅시다. API 클라이언트는 매 순간 접속하여 지난 방문 이후 새롭게 발행b된 서적에 대한 도서 데이터를 다운로드 할 것 입니다. 하지만 그 이후로 새로운 도서가 나타나지 않으면, 데이터베이스에서 서적을 가져와 응답을 전체를 렌더링하여 클라이언트에게 보내는 것은 CPU의 시간과 대역폭을 낭비하는 것입니다. b이 경우, API에게 최근의 업데이트 도서에 대해 묻는것이 보다 나은 방법입니다.
\nURLconf 에서 URL을 book list 뷰와 매핑합니다:
\nfrom django.urls import path\nfrom books.views import BookListView\n\nurlpatterns = [\n path('books/', BookListView.as_view()),\n]\n그리고 뷰에서는:
\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 headers={'Last-Modified': last_book.publication_date.strftime('%a, %d %b %Y %H:%M:%S GMT')},\n )\n return response\nIf the view is accessed from a GET request, an object list is returned in\nthe response (using the book_list.html template). But if the client issues\na HEAD request, the response has an empty body and the Last-Modified\nheader indicates when the most recent book was published. Based on this\ninformation, the client may or may not download the full object list.