This specification defines the role of a function invoker and how it interacts with other components in the riff ecosystem, namely a streaming processor and a function. The aim of this document is to formaly describe the protocol an invoker must adhere to, as well as prescribe a recommended way to build and package such an invoker.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119.
- Role of an invoker
- Streaming Specification
- Request/Reply Specification
- Packaging an invoker for riff
- use of buildpacks
- contract with riff cli: riff.toml
- how to get "http for free"
- Glossary