Context Navigation

Changes between Initial Version and Version 3 of Ticket #33611

Ticket #33611
- Property Cc Andrew Godwin added
- Property Component HTTP handling → Generic views

-              initial
+              v3
 The current [https://docs.djangoproject.com/en/4.0/topics/async/#async-views topic docs for Async views] say this about class-based views:
 > For a class-based view, this means making its __call__() method an async def (not its __init__() or as_view()).
+> For a class-based view, this means making its `__call__()` method an async def (not its `__init__()` or `as_view()`).
 This isn't really appropriate for Django's class-based views:
 * We don't implement `__call__()`, rather going via `as_view() — for a per-request instance — and then `dispatch()`.
 * Users expect to implement the HTTP method handlers — `get`, `post`, and so on — rather than these ''more internal'' bits.
+* We don't implement `__call__()`, rather going via `as_view()` — for a per-request instance — and then `dispatch()`.
+* Users expect to implement the HTTP method handlers — `get()`, `post()`, and so on — rather than these ''more internal'' bits.
 Ideally we'd allow specifying `async def` at the method handler level, to allow using `await` in the handler, and writing views such as this: