Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3425794
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T06:38:11+00:00 2026-05-18T06:38:11+00:00

so I have been playing around with django for a bit and I really

  • 0

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’.

Here is my current view of client-server-django world, which is very rough and will probably make your toenails curl (sorry)…

  1. The browser sends a Http request to the server.
  2. The server does its magic and dumps the request via the CGI to django (?)
  3. Some part of django (which?) receives the request and turns it into a django request object.
  4. The request object wanders on some nebulous paths through the middleware which does strange things with it.
  5. 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.
  6. 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… 😉
  7. The view functions returns an HttpResponse object, I guess this is returned on some nebulous paths to the CGI.
  8. Webserver takes over again and sends the Http response to the client.

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

  1. You could clear up my grosses misconseptions
  2. 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
  3. 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.

thanks a lot
Paul

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T06:38:12+00:00Added an answer on May 18, 2026 at 6:38 am

    Watch James Bennett’s Django in Depth tutorial from Pycon 2015.

    From the Pycon website, here’s the abstract of James’ talk:

    Most books, tutorials and other documentation for Django take a high-level approach to its components and APIs, and so barely scratch the surface of the framework. In this tutorial, however, we’ll take a detailed look under the hood, covering everything from the guts of the ORM to the innards of the template system to how the admin interface really works.

    Whether you’re the newest of newbies or the most seasoned of application developers, you’ll come away with a deeper knowledge of Django, and a plethora of new tips and tricks you can use in your own applications.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have been playing around with D 2.0 a bit today mostly because of
I have been playing around with this problem since yesterday. I can't seem to
I have been playing around with the postgresql.conf file for a couple days now.
I have been playing around with the EF to see what it can handle.
I have been working with PostgreSQL, playing around with Wikipedia's millions of hyperlinks and
I have been playing with this for a while, but the closest I have
I have been playing with the demo code from this msdn article by Jeffrey
Have been playing around with linq but there is one thing I cant seem
I have been playing around with writing some simple card games in Python for
I have been playing around in expect recently and I for the life of

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.