The current control.proto contains Processing Instructions for actions like retrieving an EventProcessor it's status, calling a release/split/merge of a segment and starting and stopping one.
Each operation introduces a fairly simple change to the API, but a change nonetheless.
Ideally, we'd have a more generic API, which contains an instruction type and a 'serialized payload' of the processing instruction which is sent. That way, we're more future proof for follow up instruction's we'd want to add.
The current
control.protocontains Processing Instructions for actions like retrieving anEventProcessorit's status, calling a release/split/merge of a segment and starting and stopping one.Each operation introduces a fairly simple change to the API, but a change nonetheless.
Ideally, we'd have a more generic API, which contains an instruction type and a 'serialized payload' of the processing instruction which is sent. That way, we're more future proof for follow up instruction's we'd want to add.