Interact with RemoteDispatcher and Publisher? about bluesky-browser

[danielballan]

It does now, unless I've misunderstood?

$ bluesky-browser --help
usage: bluesky-browser [-h] [-z ZMQ_ADDRESS] [--verbose] [--demo] catalog

Prototype bluesky data browser

positional arguments:
  catalog

optional arguments:
  -h, --help            show this help message and exit
  -z ZMQ_ADDRESS, --zmq-address ZMQ_ADDRESS
                        0MQ remote dispatcher address (host:port)
  --verbose, -v
  --demo                Launch the app with example data.

version 0.post128+g418aabe

[CJ-Wright]

Does it take messages from there as well and hand them to the RunRouter?

[danielballan]

Yes. The documents from 0MQ are pushed through the same RunRouter as the documents from "opening" a run in the search results.

[danielballan]

To be more specific, documents are piped from a 0MQ RemoteDispatcher into a Qt Signal

bluesky-browser/bluesky_browser/zmq.py

Lines 16 to 23 in 23faf61

	self.dispatcher = RemoteDispatcher(zmq_address)
	def callback(name, doc):
	if name == 'start':
	log.debug("New streaming Run: uid=%r", doc['uid'])
	self.documents.emit((name, doc))
	self.dispatcher.subscribe(callback)

and consumed by the Viewer widget:

bluesky-browser/bluesky_browser/main.py

Lines 93 to 96 in 23faf61

	if zmq_address:
	self.consumer_thread = ConsumerThread(zmq_address=zmq_address)
	self.consumer_thread.documents.connect(self.viewer.consumer)
	self.consumer_thread.start()