Re:Machinery: An asynchronous task/job queue for Golang
by richardknop on Sunday May 10, 2015 @06:48PM
(#9521735)
There is a very basic client implementation of client in examples/send/send.go.
This is a very early stage project though. I agree that some parts of the API might need to be rethought and other approaches considered.
I think a full example should involve the client part as well ( in order to remain typed along the chain, and have the json format describing the task an implementation detail).
Edit : i didn't read properly, the readme also describes how a task is created. I didn't expect it to use a low level format though. Why not relying directly on the type of the task ( "AddTask") rather than asking for a "add" string parameter ?