Hi ruffeo wrote: > Does anyone know how to develop a complex django project in a 3 tiered > network environment, still using the MCV architecture? > > I.E. Web Server (view and control code), App Server (model code), and > Database Server
model- representation that needs to be modeled into the db (data model e.g models.py) template- your user-facing code so it differentiates how your data is presented (e.g templates/*) view- maps your uri specific code to callback functions (e.g in views.py) which should be resolvable by the URLResolver (to be defined in URLConf) MTV - this is what Django calls MVC (in that order) DB - Django's "python manage.py syncdb" pulls the class definition from the Model (e.g. models.py) and then inserts them into the DB. This ORM design is really powerful as we get db<->application_code mapping essentially for free. A DB can be another tier here that exists seperately. Web server - Apache, FastCGI, any WSGI-compliant server etc.. (Django provides lightweight devel server too) On the topic of Application server, Djangobook.com puts it really nicely - "At its core, the philosophy of shared nothing is really just the application of loose coupling to the entire software stack. This architecture arose in direct response to what was at the time the prevailing architecture: a monolithic Web application server that encapsulates the language, database, and Web server — even parts of the operating system — into a single process (e.g., Java)."[1] Others could possibly add more to your query (because I've yet to learn Django properly myself) but from what I've understood Django does not need a app server! Cheers, Ishwor [1] http://www.djangobook.com/en/1.0/chapter20/
smime.p7s
Description: S/MIME Cryptographic Signature
