Confirmed users
920
edits
MDN/Archives/Kuma/Scripting: Difference between revisions
Jump to navigation
Jump to search
→Proposed solution #1
LesOrchard (talk | contribs) |
LesOrchard (talk | contribs) |
||
| Line 128: | Line 128: | ||
** Something like what [http://developer.mindtouch.com/en/docs/DekiScript/Reference/Wiki_Functions_and_Variables DekiScript offers for wiki functions and variables] | ** Something like what [http://developer.mindtouch.com/en/docs/DekiScript/Reference/Wiki_Functions_and_Variables DekiScript offers for wiki functions and variables] | ||
* Plentiful and intelligent HTTP-based caching | * Plentiful and intelligent HTTP-based caching | ||
==== Oh look, a drawring ==== | |||
[[File:Kumascript.png|1000px|Kuma script flow]] | [[File:Kumascript.png|1000px|Kuma script flow]] | ||
More notes: | |||
* If the caching works right, we should be able to almost never load & compile templates unless they're edited. (Cache invalidation? HEAD requests before GET requests?) | |||
* When a Kuma wiki page is edited, the last-cached KumaScript response is discarded. | |||
* To support preview functionality, we can accept HTTP POST of arbitrary page source at the start of the KumaScript flow. Not cached, which is a feature. | |||
=== Code samples (imaginary) === | === Code samples (imaginary) === | ||