From 3c7e86cd326eeed017de4edb9e4db3d0f34fae5c Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Sun, 16 Feb 2025 17:37:54 +0000 Subject: [PATCH] article URL on templates - online edit of handbook/troggle/trogdjango.html --- handbook/troggle/trogdjango.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/troggle/trogdjango.html b/handbook/troggle/trogdjango.html index a14eddce5..7b3a64085 100644 --- a/handbook/troggle/trogdjango.html +++ b/handbook/troggle/trogdjango.html @@ -61,7 +61,7 @@ href="https://docs.djangoproject.com/en/dev/misc/design-philosophies/">loosely c
  • SQL database: mapping to/from python objects and indexing/access routines for all the entries (sqlite, MySQL, MariaDB, postgres all work). This is where the multi-user synchronisation happens too.
  • request/response (http GET/POST) including access control and security middleware. We could never keep up with web security if we didn't use a well-supported system for this.
  • URL mapping/dispatch which matches a requested URL with a chunk of python code, and vice versa (declarative and bidrectional). "Cool URIs don't change." -
  • templates which format the results of data queries into HTML pages or JSON data exports +
  • templates which format the results of data queries into HTML pages or JSON data exports. [2025 article on Django templates]

    See the django design philosophy on 'loose coupling and tight cohesion'. Note that having a URL dispatcher that supports