-
Notifications
You must be signed in to change notification settings - Fork 198
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
zmq router and udp router are *forwarders* : they receive a message a…
…nd forward it on use the radio interface to make it clear that that is what they are doing the intention there is to make it cleaner to swap out *how* they perform forwarding - clarifying that these two threads are forwarders, not doing anything else to the message flow. after this patch, my intention is that: i) the ZMQ listener moves into the db manager and there is no multiprocessing queue forwarding from outside of the db manager ii) the UDP listener, all that is left, means this can be renamed the UDP radio receiver, sitting as a processes alongside the filesystem radio receiver (and eventually any other radio receivers) compare to how the interchange sends htexradio messages onwards via some arbitrary other radio (which right now is always the ZMQRadioSender) -- rather than having its own radio code. the previous multiprocessing queue code should be replaced with multiprocessing queue sender
- Loading branch information
1 parent
22e62ae
commit 39fc0de
Showing
2 changed files
with
11 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters