{ "href": "/post/2022/09/23/in-template-response-building/", "relId": "2022/09/23/in-template-response-building", "title": "In-Template Response Building", "author": "pmjones", "tags": [ { "href": "/tag/programming/", "relId": "programming", "title": "Programming", "author": null, "created": null, "updated": [], "markup": "markdown" }, { "href": "/tag/php/", "relId": "php", "title": "PHP", "author": null, "created": null, "updated": [], "markup": "markdown" }, { "href": "/tag/qiq/", "relId": "qiq", "title": "Qiq", "author": null, "created": "2021-10-20 16:48:23 UTC", "updated": [ "2021-10-20 16:48:23 UTC" ], "markup": "markdown" }, { "href": "/tag/sapien/", "relId": "sapien", "title": "Sapien", "author": null, "created": "2021-11-09 16:57:39 UTC", "updated": [ "2021-11-09 16:57:39 UTC" ], "markup": "markdown" } ], "created": "2022-09-23 12:52:28 UTC", "updated": [ "2022-09-23 12:52:28 UTC", "2022-09-23 12:53:10 UTC", "2022-09-23 15:37:50 UTC", "2022-09-23 21:44:20 UTC", "2022-09-23 21:47:59 UTC", "2022-09-23 21:50:34 UTC", "2022-09-23 21:50:54 UTC", "2022-09-23 21:52:47 UTC", "2022-09-23 21:53:29 UTC", "2022-09-23 21:54:32 UTC", "2022-09-23 21:54:46 UTC", "2022-09-29 16:48:16 UTC", "2022-10-03 20:19:46 UTC", "2022-10-13 14:17:59 UTC" ], "markup": "markdown", "html": "

I am fond of saying that in server-side applications, the Template is not the View. Instead, the HTTP Response is the View. That is, the Response presented by the server is not only the templated content; the presentation includes both the headers and the content in the Response.

\n

But what if you can build the HTTP Response inside a Template?

\n

That is just what the new Qiq helpers using Sapien, let you do. Using the qiq/helper-sapien package, you can set Response headers, cookies, etc. from inside your template code ...

\n
{{ response()->setVersion('1.1') }}\n{{ response()->setCode(200) }}\n{{ response()->setHeader('content-type', 'text/plain') }}\nHello, world!\n
\n

... and get back a complete Response object for sending:

\n
$response = $template->response()->render($template);\n$response->send();\n
\n

In addition, you can use setFile() to build a file-download Response ...

\n
{{ response()->setFile('/path/to/file.txt') }}\n
\n

... or setJson() to build a JSON Response:

\n
{{ response()->setJson(['foo' => 'bar']) }}\n
\n

Does this mean the Template is the View after all? If so, it's only because the entire Response is built by the Template. Perhaps this could be called a ResponseView.

\n

Will this make a Qiq template into a complete ADR Responder? Maybe, maybe not -- but it does mean that Responder implementations have the option to hand off most or all Response-building work to Qiq template code.

\n" }