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.

Sign up for GitHub

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

Jump to bottom

Backporting of Message Channel Support #1837

Closed
lee212 opened this issue Mar 20, 2019 · 2 comments
Closed

Backporting of Message Channel Support #1837

lee212 opened this issue Mar 20, 2019 · 2 comments
Labels
priority:low priority:v2 topic:communication type:feature
Milestone
Version 2.0

Comments

@lee212
Copy link
Contributor

lee212 commented Mar 20, 2019

This is about additional ZMQ bridges for application use, for example, pushing a message instead of writing an intermediate file between ENTK tasks. This feature is scheduled to Version 2 but backporting is requested to leverage this new feature beforehand.
@andre-merzky
Copy link
Member

This can likely happen before v2, thus left open.

@andre-merzky andre-merzky added this to the Future Release milestone Apr 3, 2019
@andre-merzky
Copy link
Member

This is implemented now - have a look at this example on how to use it. The same directory also contain the worker and clients using the comm channels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority:low priority:v2 topic:communication type:feature
Projects
None yet
Milestone
Version 2.0
Development

No branches or pull requests
2 participants
@andre-merzky @lee212