Documentation
¶
Overview ¶
Package remote contains an ordinary remote component handler. The handler receives bound configuration and providers through the same DI path as an application-defined handler. Shared remote call planning lives in runtime/remote.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Handler ¶
type Handler[O any] struct { Mapper *core.Mapper `bind:"kind=remote_mapper,required"` HTTP xhttp.Provider `bind:"kind=http_client"` MCP xmcp.Provider `bind:"kind=mcp_client"` Cache xcache.Provider `bind:"kind=cache"` }
Handler is an ordinary component handler over Input and a user-declared output. Native Bindly resolves its static dependencies once, during runtime registration, before Exec can run. Register it like any other contract:
custom.New(&remote.Handler[access.Context]{})
type Input ¶
type Input struct {
Token string `parameter:"Token,kind=header,in=Authorization,required"`
Remote core.Config `parameter:"Remote,kind=const,in=Remote"`
}
Input is the shipped per-request input: one caller credential forwarded verbatim by a request mapping and the typed configuration constant. Component metadata may rename the incoming header; nothing here inspects or rewrites the credential. Applications with other request shapes declare their own input and call Mapper.HTTP or Mapper.MCP from Exec.