23 lines
1.3 KiB
Plaintext
23 lines
1.3 KiB
Plaintext
:sig
|
|
RENDER(Request& context)
|
|
|
|
:desc
|
|
Defines the main HTTP render handler for the current `.uce` page.
|
|
|
|
When a page is requested over HTTP, the runtime loads the target file and calls its `RENDER(Request& context)` function.
|
|
|
|
The default page entrypoint is always the plain `RENDER(Request& context)` handler.
|
|
|
|
Reusable component handlers now live on `COMPONENT(Request& context)` and `COMPONENT:NAME(Request& context)`. The component helpers call those handlers, not `RENDER()`.
|
|
|
|
The request environment is passed explicitly through `context`, including params, cookies, post data, session state, headers, uploaded files, and the current `context.call` tree.
|
|
|
|
For a normal direct page request, `context.call` starts empty.
|
|
|
|
If the page is invoked from another UCE file via `unit_render(file_name, context)`, the callee receives that same `context`.
|
|
|
|
Pages intended to serve WebSocket traffic may expose both `RENDER(Request& context)` and `WS(Request& context)`. Files may also define `COMPONENT()` handlers when they intentionally need both page and component behavior in one unit. In that case `RENDER(Request& context)` serves the direct HTTP response, `WS(Request& context)` handles subsequent WebSocket messages, and `COMPONENT()` remains available only through the component helpers.
|
|
|
|
:see
|
|
>ob
|