Expand description
ZMQ message framing on the frontend–engine sockets.
- Input (frontend ROUTER to engine DEALER):
[type, payload, aux...].typeis one byte so the engine dispatches without decoding: ADD carries aTokenizedGenerateReqInputwhose tensors may reference theauxframes; ABORT carries a msgpack list of request ids; CONTROL carries aControlRequest. - Output (engine PUSH to frontend PULL): a
BatchTokenIDOutSlimmessage, aControlOutput(told apart by its tag), or the single frameENGINE_CORE_DEADwhen the engine exits.
Enums§
- Engine
Output - A message on the engine’s output socket.
- Engine
Request - A message on the engine’s input socket.
Constants§
- ENGINE_
CORE_ DEAD - The frame an engine sends on its output socket when it shuts down; the frontend then treats the engine as dead.
- REQ_
TYPE_ ABORT - Type byte of an ABORT message.
- REQ_
TYPE_ ADD - Type byte of an ADD message.
- REQ_
TYPE_ CONTROL - Type byte of a CONTROL message.
Functions§
- engine_
identity - The ZMQ routing identity of engine
engine_index: its index as two little-endian bytes.