Server.RequestId
luastra/serverServer.RequestId is an opaque numeric identifier allocated for one asynchronous operation. Store it with the operation's purpose so app.resolve can correlate out-of-order completions without inspecting payload text.
Before you use it
Add luastra/server to this module's dependencies in luastra.json, then import it with require("luastra/server"). Declare rpc.call in luastra.json and configure a declared backend operation with a deployed trusted handler. Application code should prefer its generated operation function and decoder.
How it fits
The type describes request options, v2 limits, nullable values, public errors, or the tagged envelope-decoding result.
When to use it
Use Server.RequestId as the key in a pending-operation map after starting an asynchronous Server request. Match and remove that key in app.resolve instead of relying on completion order.
Fields or definition
| Parameter | Type / values | Description |
|---|---|---|
| definition | number | Exact alias, union, or callable contract represented by Server.RequestId. |
What happens next
A checked request, result, limit, nullable-value, or public-error annotation.
Failures and fixes
Handle transport failure, envelope decode failure, and domain validation failure separately. The static web build does not deploy trusted backend handlers, credentials, or production operations for you.
Availability
Public-source alpha API in 0.5.0-alpha; production backend deployment remains application-owned.
Exact declaration
export type RequestId = number