Skip to content
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

Guarantees of # publishes / # messages received per topic #26

Open
skugele opened this issue Nov 13, 2016 · 0 comments
Open

Guarantees of # publishes / # messages received per topic #26

skugele opened this issue Nov 13, 2016 · 0 comments

Comments

@skugele
Copy link
Member

skugele commented Nov 13, 2016

In processes and threads that use message passing, we need to guarantee that those processes and threads operate under the following constraints:

  1. Receive at most a single message from each subscribed to topic per invocation
  2. Publish at most a single message to each published to topic per invocation

To do otherwise would be rude.

One idea that was discussed for achieving this would be to maintain a map for each topic, and to set a boolean value whenever a message is published or subscribed to/from that topic. If publishing or subscribing happens 2x, then return a warning or error and prevent the operation. Upon subsequent invocations of the process or thread (for example, between calls to a module's "call" method), the topic map could be cleared to enable publishing/subscribing again.

It's very important that this solution work for all types of FrameworkRunnables.

@skugele skugele added this to Backlog in LidaPy Kanban Board Jul 1, 2017
@skugele skugele moved this from Backlog to In Progress in LidaPy Kanban Board Jul 3, 2017
@skugele skugele moved this from In Progress to Backlog in LidaPy Kanban Board Jul 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants