piker/piker
Tyler Goodlet 20250961a6 Begin to use `@tractor.msg.pub` throughout streaming API
Since the new FSP system will require time aligned data amongst actors,
it makes sense to share broker data feeds as much as possible on a local
system. There doesn't seem to be downside to this approach either since
if not fanning-out in our code, the broker (server) has to do it anyway
(and who knows how junk their implementation is) though with more
clients, sockets etc. in memory on our end. It also preps the code for
introducing a more "serious" pub-sub systems like zeromq/nanomessage.
2020-08-19 07:51:43 -04:00
..
brokers Begin to use `@tractor.msg.pub` throughout streaming API 2020-08-19 07:51:43 -04:00
cli Add `services` cmd for monitoring actors 2020-08-03 21:31:56 -04:00
data Begin to use `@tractor.msg.pub` throughout streaming API 2020-08-19 07:51:43 -04:00
testing Import client for now until we make a proper shim 2018-02-12 10:35:54 -05:00
ui Use partial, pass kwargs to `tractor._main()` 2020-08-19 07:41:18 -04:00
watchlists Reord watchlist cmds into new package 2020-05-26 14:49:50 -04:00
__init__.py Use msgpack-numpy 2020-07-03 18:32:40 -04:00
_async_utils.py An explicit name is prolly better 2018-11-25 19:23:07 -05:00
calc.py Allow specifying number of displayed digits 2018-11-13 18:42:34 -05:00
log.py Delegate logging to `tractor` 2020-02-29 12:29:20 -05:00