The onion model on the Django middleware documentation page might also help -
http://docs.djangoproject.com/en/dev/topics/http/middleware/ The rest of it (how it is handled from the WSGI handler etc.) is really an internal matter. Unless you want to contribute to Django or create some custom version of it, there isn't much need/point in fiddling with it, because you'll just be asking for pain when there are updates. There should be enough extensibility points for you already. On 20 June 2010 14:47, Kenneth Gonsalves <[email protected]> wrote: > On Saturday 19 June 2010 18:04:33 Sameer Rahmani wrote: >> i want to know about a django project life cycle, can any body help me >> please? >> >> i want to know how a django project run under wsgi and development server ? >> which files runs first? >> does a project run in each request? or it remain in memory ? >> and any other useful information >> > > well first thing is that django is a framework and not a server. So basically > the flow is precisely the same as ordinary cgi programming. You type in a url > which calls a function which does something and displays a page. > -- > Regards > Kenneth Gonsalves > Senior Associate > NRC-FOSS at AU-KBC > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
