> No, Django doesn't talk HTTP -- Django talks WSGI or CGI. That hides many of the details of the protocol in use -- I imagine that you could run Django with a

> No, Django doesn't talk HTTP -- Django talks WSGI or CGI. That hides many of the details of the protocol in use -- I imagine that you could run Django with a server that sends/receives web requests over FTP. I don't know how you would make e.g that[1] work on FTP. Basically you would end up encapsulating HTTP inside FTP, not using one in place of the other. A CGI script takes raw (yet conveniently split by the web server) HTTP data from ENV vars and stdin, and outputs HTTP data directly to stdout. Django HttpRequest and HttpResponse object merely provides a convenient helper for that and does not actually abstract anything. The web server pipes the response as is straight to the client via TCP (unless there is SSL, where it will just obliviously encrypt the stream). To comply with that, as SPDY is a replacement to HTTP, mod_spdy transcodes stuff live [2]. [1] https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.HttpRequest.META https://docs.djangoproject.com/en/dev/ref/request-response/#... [2] http://code.google.com/p/mod-spdy/wiki/Design http://code.google.com/p/mod-spdy/wiki/Design