From deedf6957d14c2808c00a009ac2c1d4528cb80c9 Mon Sep 17 00:00:00 2001
From: Tom Christie
Date: Sat, 1 Sep 2012 20:26:27 +0100
Subject: REST framework 2 docs

---
 docs/api-guide/responses.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 docs/api-guide/responses.md

(limited to 'docs/api-guide/responses.md')

diff --git a/docs/api-guide/responses.md b/docs/api-guide/responses.md
new file mode 100644
index 00000000..38f6e8cb
--- /dev/null
+++ b/docs/api-guide/responses.md
@@ -0,0 +1,23 @@
+# Responses
+
+> Unlike basic HttpResponse objects, TemplateResponse objects retain the details of the context that was provided by the view to compute the response. The final output of the response is not computed until it is needed, later in the response process.
+>
+> — [Django documentation][cite]
+
+REST framework supports HTTP content negotiation by providing a `Response` class which allows you to return content that can be rendered into multiple content types, depending on the client request.
+
+The `Response` class subclasses Django's `TemplateResponse`.  `Response` objects are initialised with content, which should consist of native python primatives.  REST framework then uses standard HTTP content negotiation to determine how it should render the final response content.
+
+There's no requirement for you to use the `Response` class, you can also return regular `HttpResponse` objects from your views if you want, but it does provide a better interface for returning Web API responses.
+
+## Response(content, headers=None,  renderers=None, view=None, format=None, status=None)
+
+
+## .renderers
+
+## .view
+
+## .format
+
+
+[cite]: https://docs.djangoproject.com/en/dev/ref/template-response/
\ No newline at end of file
-- 
cgit v1.2.3