-
Notifications
You must be signed in to change notification settings - Fork 0
Drivers
There're two simple types of timers available for now — recurring-timer and drifting-timer. The only difference is that the drifting timer will not start another job if the previous one is not yet completed, even though the time is right.
-
interval, milliseconds - time between job invocations.
The filesystem-monitor will watch for changes in the specified path in the best possible way on your platform and trigger the job when such changes happen (new or deleted file, file changes, etc.)
-
path, string - filesystem location to watch.
TBD.
The zeromq-server and zeromq-sink will listen on the specified port for requests and trigger new jobs, pushing the received data into the slaves. The difference between server and sink is that sink doesn't send any responses back to the clients or even imply their presence, so it's a good way to build pipelines.
No magic here, send your messages the normal way you do when using ZeroMQ. The only feature is that if you send a multipart message, it will be treated as a bulk request, triggering a new job for every message part.
-
endpoint, string - ZeroMQ-specific connection string, for example,tcp://*:6000oripc:///var/run/sink. If omitted, the server will assign an endpoint automatically. -
backlog, positive integer - maximum number of outstanding connections waiting to be accepted on the socket. Default value is1000. -
linger, milliseconds - how much time to wait on server termination for the outstanding responses to be sent to the clients. Default value is0, which means that all the outstanding responses should be dropped immediately.