---
title: "基于类的视图"
version: 2.1
locale: zh-hans
source: https://docs.djangoproject.com/zh-hans/2.1/topics/class-based-views/
canonical: https://djangodocs.dev/zh-hans/2.1/topics/class-based-views/
---
# 基于类的视图

视图是可调用的，能接受用户的请求并返回响应。视图远不只是个函数，Django提供了一些可用作视图的类的示例，允许你通过继承和复用构建自己的视图并且复用这些代码。虽然接下来还会介绍一些用于简单任务的通用视图，但你可能想自己设计可复用的视图结构，以便针对某些特殊场景。详情请见 class-based views reference documentation\</ref/class-based-views/index\> 。

- [基于类的视图](/zh-hans/2.1/topics/class-based-views/intro/)
- [Built-in class-based generic views](/zh-hans/2.1/topics/class-based-views/generic-display/)
- [Form handling with class-based views](/zh-hans/2.1/topics/class-based-views/generic-editing/)
- [Using mixins with class-based views](/zh-hans/2.1/topics/class-based-views/mixins/)

## Basic examples

Django provides base view classes which will suit a wide range of applications.
All views inherit from the [`View`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.View) class, which
handles linking the view in to the URLs, HTTP method dispatching and other
simple features. [`RedirectView`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.RedirectView) is for a
simple HTTP redirect, and [`TemplateView`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.TemplateView)
extends the base class to make it also render a template.

## Simple usage in your URLconf

The simplest way to use generic views is to create them directly in your
URLconf. If you're only changing a few simple attributes on a class-based view,
you can simply pass them into the
[`as_view()`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.View.as_view) method call itself:

```
from django.urls import path
from django.views.generic import TemplateView

urlpatterns = [
    path('about/', TemplateView.as_view(template_name="about.html")),
]
```

Any arguments passed to [`as_view()`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.View.as_view) will
override attributes set on the class. In this example, we set `template_name`
on the `TemplateView`. A similar overriding pattern can be used for the
`url` attribute on [`RedirectView`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.RedirectView).

## Subclassing generic views

The second, more powerful way to use generic views is to inherit from an
existing view and override attributes (such as the `template_name`) or
methods (such as `get_context_data`) in your subclass to provide new values
or methods. Consider, for example, a view that just displays one template,
`about.html`. Django has a generic view to do this -
[`TemplateView`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.TemplateView) \- so we can just subclass it,
and override the template name:

```
# some_app/views.py
from django.views.generic import TemplateView

class AboutView(TemplateView):
    template_name = "about.html"
```

Then we just need to add this new view into our URLconf.
[`TemplateView`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.TemplateView) is a class, not a function,
so we point the URL to the [`as_view()`](/zh-hans/2.1/ref/class-based-views/base/#django.views.generic.base.View.as_view)
class method instead, which provides a function-like entry to class-based
views:

```
# urls.py
from django.urls import path
from some_app.views import AboutView

urlpatterns = [
    path('about/', AboutView.as_view()),
]
```

For more information on how to use the built in generic views, consult the next
topic on [generic class-based views](/zh-hans/2.1/topics/class-based-views/generic-display/).

### Supporting other HTTP methods

Suppose somebody wants to access our book library over HTTP using the views
as an API. The API client would connect every now and then and download book
data for the books published since last visit. But if no new books appeared
since then, it is a waste of CPU time and bandwidth to fetch the books from the
database, render a full response and send it to the client. It might be
preferable to ask the API when the most recent book was published.

We map the URL to book list view in the URLconf:

```
from django.urls import path
from books.views import BookListView

urlpatterns = [
    path('books/', BookListView.as_view()),
]
```

And the view:

```
from django.http import HttpResponse
from django.views.generic import ListView
from books.models import Book

class BookListView(ListView):
    model = Book

    def head(self, *args, **kwargs):
        last_book = self.get_queryset().latest('publication_date')
        response = HttpResponse('')
        # RFC 1123 date format
        response['Last-Modified'] = last_book.publication_date.strftime('%a, %d %b %Y %H:%M:%S GMT')
        return response
```

If the view is accessed from a `GET` request, a plain-and-simple object
list is returned in the response (using `book_list.html` template). But if
the client issues a `HEAD` request, the response has an empty body and
the `Last-Modified` header indicates when the most recent book was published.
Based on this information, the client may or may not download the full object
list.