On Sun, Jul 15, 2012 at 10:30 AM, Stephan Beal <[email protected]>wrote:
> either the client or server side. As of yesterday/this morning th1 script > has access to the GET/POST environment, the database, and an output > buffering layer (your merging example is a case where the buffering layer > is useful), so it's quickly becoming more useful for this (and these parts > can be used with the existing header/footer mechanism - my local repo now > has th1-fetched db data scattered around my header). > Which reminds me: now that th1 can access get/post args, the header, footer, and any docs/pages/commands we make th1-aware can behave more dynamically. For example: http://..../?foo=3 Server-side: set foo [argv getint foo "" 0] if { 0 == $foo } { ... default behaviour } else { render_doc doc_$foo } this could be extended to support cookies (if it doesn't already - i think fossil currently only reads its own authentication cookie?), allowing such state to persist across calls. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
