Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I best find out how django works internally?
    primarykey
    data
    text
    <p>so I have been playing around with django for a bit and I really do like this framework. However, I would like to understand better how it actually works 'under the covers'. </p> <p>Here is my current view of client-server-django world, which is very rough and will probably make your toenails curl (sorry)...</p> <ol> <li>The browser sends a Http request to the server.</li> <li>The server does its magic and dumps the request via the CGI to django (?)</li> <li>Some part of django (which?) receives the request and turns it into a django request object.</li> <li>The request object wanders on some nebulous paths through the middleware which does strange things with it.</li> <li>The request object finally ends up in some function (which?) which looks at the urls, takes the patterns out of urls.py and calls up a view function.</li> <li>The view functions do their magic (with models and templates as partners in vice) , this is probably where I have the strongest illusion of understanding (well, apart from the database abstraction magic, that is... ;)</li> <li>The view functions returns an HttpResponse object, I guess this is returned on some nebulous paths to the CGI.</li> <li>Webserver takes over again and sends the Http response to the client.</li> </ol> <p>Ok, so what the heck is my question you ask? Well, how does this all work, really? I am not expecting that you spoon-feed me everything... I suspect that the answer will ultimately be to "read the source, luke", however, I would be grateful if</p> <ol> <li>You could clear up my grosses misconseptions</li> <li>tell me where to start? What I would like to do is grap a debugger and just walk through the process a couple of times, but I don't really know where to get started</li> <li>you could point me to any documents that explain this well... yes, I have heard of this google thing but haven't really found anything super-useful.</li> </ol> <p>thanks a lot Paul</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload