You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What if we have some code in C, Perl, Ruby or another language and want to have it as a worker inside a pipeline? Currently we can't run do this unless we create a Python worker that executes a process, calling the external code.
A possible implementation to solve this problem is to create a "worker socket" (or other kind of inter-process communication, maybe using ZeroMQ) on Broker so any process that connects there (and authenticates?) can register itself as a worker, independent of how (which language) it's implemented.
The text was updated successfully, but these errors were encountered:
What if we have some code in C, Perl, Ruby or another language and want to have it as a worker inside a pipeline? Currently we can't run do this unless we create a Python worker that executes a process, calling the external code.
A possible implementation to solve this problem is to create a "worker socket" (or other kind of inter-process communication, maybe using ZeroMQ) on
Broker
so any process that connects there (and authenticates?) can register itself as a worker, independent of how (which language) it's implemented.The text was updated successfully, but these errors were encountered: