public
Description: An Erlang client library for beanstalkd
Homepage: http://tfletcher.com/dev/erlang-beanstalk
Clone URL: git://github.com/tim/erlang-beanstalk.git
tim (author)
Sun May 04 03:53:16 -0700 2008
commit  4c218a12a59888842b301253831935f2c5341833
tree    68e1ddd29f0b0aac758b0a4dbf18f7736556f5e3
parent  6a27bffcfe94f2811b239b6b76d7d1c9673bdc99
name age message
file .gitignore Sun Apr 27 11:39:14 -0700 2008 Added an Emakefile (and a Makefile for the lazy... [dustin]
file Emakefile Sun Apr 27 11:39:14 -0700 2008 Added an Emakefile (and a Makefile for the lazy... [dustin]
file License.txt Sun May 04 03:49:43 -0700 2008 Licenses are boring. [tim]
file Makefile Sun Apr 27 11:39:14 -0700 2008 Added an Emakefile (and a Makefile for the lazy... [dustin]
file README.txt Sun May 04 03:45:39 -0700 2008 Credits. [tim]
directory src/ Sun May 04 03:53:16 -0700 2008 Handle other tcp messages. [tim]
README.txt
================
Erlang-Beanstalk
================


What is this?
-------------

An Erlang module that wraps the beanstalkd protocol.


What is beanstalkd?
-------------------

A fast, distributed, in-memory workqueue service.

See http://xph.us/software/beanstalkd/ for more information,
and links to clients in other languages.


How do I use it?
----------------

First, make sure both of the modules are compiled, and that you
have an instance of beanstalkd running in the background. Then
you can connect to it like so (using whatever host and port values
are appropriate for you):

  {ok, Socket} = beanstalk:connect(_Host="0.0.0.0", _Port=3000).

At the moment this is just a direct call to gen_tcp:connect/3.

Jobs are manipulated using the beanstalk_job module. To create
a new job, pass a string or a binary to beanstalk_job:new/1:

  Job = beanstalk_job:new("hello").

You can alter the defaults using beanstalk_job:with/3, e.g.,

  DelayedJob = beanstalk_job:with(delay, 30, Job).

All the functions in the beanstalk module (apart from connect/2)
correspond to calls in the beanstalkd protocol. Each expects to
be given the socket connection as the last argument. For example:

  {inserted, JobID} = beanstalk:put(Job, Socket).

  {reserved, Job} = beanstalk:reserve(Socket).

  deleted = beanstalk:delete(JobID, Socket).

And so on.


WTF?
----

Found a bug? Think I could have done something better?

Don't let it trouble you :) Let me know!


Who should I contact?
---------------------

Tim Fletcher (tfletcher.com).


Acknowledgements
----------------

Thanks to Dustin Sallings for introducing me to Emakefiles.