Clearer description

[nodefish]

Hi,

This project is great but I skipped it numerous times while searching for a decent beanstalkd client, because I thought this was only for the job consumer (worker) side. In fact, this can actually put jobs in the queue, so generally speaking it is more than a worker. It's both a job producer and consumer, but I didn't realize that.

Please consider improving the description of the project, to show that it covers the whole producer-consumer cycle. I think more people would use it then.

Thanks

[mickhansen]

Hey there @nodefish,

I definitely see your point and i'll work on a better description.
I haven't done much "marketing" wise for any of my beanstalkd related libraries, i mainly wanted a better one personally.

[nodefish]

IMHO a couple more clarifications (e.g. does a job get buried when it fails all the retries?) and this could easily replace the other aging or overly convoluted beanstalkd clients.

[gustawdaniel]

Docs of this project is his weakest side. Fivebeans with his callback heel is better documented. Can you provide 1-2 working simple hello world examples?

What exactly are problems:

• tube - you use the same name tube as string and as object without any comment
• to many operations in callback, it should be separated on fully functional minimal examples and detailed API later