dev:server_print_templates
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dev:server_print_templates [2019/04/16 12:01] – [Proof of Concept] erickson | dev:server_print_templates [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| * Templates are compiled for printing on the server | * Templates are compiled for printing on the server | ||
| * At print time, the caller passes template data, template name, etc. to the server and receives a compiled (text, html, etc.) response. | * At print time, the caller passes template data, template name, etc. to the server and receives a compiled (text, html, etc.) response. | ||
| - | * Template content can be scrubbed on the server | + | * Template content can be scrubbed on the server |
| * We could use something like https:// | * We could use something like https:// | ||
| + | * Note we are already using server-managed templates for self-checkout receipts, some ACQ interfaces, and various others, so the general concept is not new. | ||
| ==== Proof of Concept ==== | ==== Proof of Concept ==== | ||
| Line 31: | Line 32: | ||
| * There is no environment building, etc. | * There is no environment building, etc. | ||
| * Provides an opportunity to add locale, content type, etc. support. | * Provides an opportunity to add locale, content type, etc. support. | ||
| - | * Uses a mod_perl front-end so template content can be treated like a web page where desired. | + | * Uses a mod_perl front-end so template content can be returned as-is (i.e. a text/ |
| ==== Offline Caveat ==== | ==== Offline Caveat ==== | ||
dev/server_print_templates.1555430509.txt.gz · Last modified: 2022/02/10 13:34 (external edit)