search

project8 / dripline

Slow controls for medium scale physics experiments based on AMQP centralized messaging
http://www.project8.org/dripline
1 stars 0 forks source link

broadcast command #94

Closed laroque closed 8 years ago

laroque commented 9 years ago

It would be nice to bind all endpoints to standard key for to which commands may be broadcast. The expectations are that: 1) if a particular endpoint doesn't support a response to commands from this, they will be quietly ignored 2) any response generated by these commands will be broadcasts on the alerts exchange, not reply messages

Use case: 1) I don't know what endpoints are there: broadcast get_heartbeat -> each endpoint sends an alert to some dedicated routing key... say someone should put a list of the alert exchange's reserved routing keys 2) I'm not sure which things are loggers, but I've started everything up and I want to ensure they are running: broadcast start_logging -> everything that is a spime enables logging (values start going out on sensor_values

laroque commented 8 years ago

this is scheduled for dripline wire protocol version 2.0

laroque commented 8 years ago

implemented and tagged