-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DataBus #2285
DataBus #2285
Conversation
e629251
to
35c4c3a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to discuss the general design of the data model and how the data is intended to be used.
b00a12e
to
067acae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest add docstrings, one method naming.
a70904b
to
e880033
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comments. Mainly about the separation of the data storage and pub/sub interface.
343984a
to
c7b5297
Compare
/build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very good in general. Suggest to change some method names.
address PR comments formatting
* check invalid input directory * check invalid input directory add doc string add doc string rename receive_messages() to receive_message() change doc str to google doc string style rebase and formats
1) remove data store scope/topic 2) add pub_sub interface and let databus implements the inferface 3) remove function_utils.py and unit tests for another PR
1) remove data store scope/topic 2) add pub_sub interface and let databus implements the inferface 3) remove function_utils.py and unit tests for another PR
a0a1e06
to
6e03a03
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/build |
/build |
Description
As part of the series PRs related to In-Process Client API Executor and WFCommAPI. This is the 1st PR for common utiliies
MessageBus is an singleton message store and publish (callbacks) structure that other can subscribe (callbacks) and receive message in callback when message is published. The event Manager can be built on top of messagebus.
The message can also send to/receive from message store for given topic.
The messagebus allows two components from strong coupling to loose coupling. For example, instead comp1 set a proprty directly on comp2. We can use messagebus, where comp1 send a message to messagebus, the comp2 receive the message from messagebus. comp2 is unaware who send the message and comp1 is unware who received the message.
Types of changes
./runtest.sh
.