ksunden / bluesky-hwproxy Goto Github PK

the cli is there, but needs to be translated into a startup dir before handing it off to the lower level code

CLI:

• list_readable
• list_configurable

e.g. describe "w1.crystal_1"

having only this process do polling of hardware and then alerting interested clients of changes scales better than having each client poll

Requires

• caching
• polling
• handshaking for clients to ask to subscribe
• probably should look at builtin zmq pub/sub infrastructure

e.g.

• set
• Flyer methods
• stage/unstage
• pause/unpause
• stop

Thus far, I've only provided the ability to read information, no set operations at all.
A full description of all protocol methods would allow a small wrapper to be used in many bluesky plans (at least ones that only use protocol methods).

Nicer python object which supports the protocols supported by this interface specifically (i.e. no setting)

These objects should be compliant to the point where they can be placed wherever a readable device is needed in a plan

So far, we assume trusted users and only provide read operations anyway (see #3).

We could:

• use the allowed plans and devices / user group code from queueserver to differentiate who is allowed to see what hardware
• somehow auth against httpserver, not currently using that project, so a little out of the loop on what is possible/easy. can we just provide additional routes to the existing server?