This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 6a27bffcfe94f2811b239b6b76d7d1c9673bdc99
tree df539e1ae14b58bf1cf0cf09258ef6ac5b9f3f50
parent d17537f77b905238d67182bb3de9e14cf57dfc0b
tree df539e1ae14b58bf1cf0cf09258ef6ac5b9f3f50
parent d17537f77b905238d67182bb3de9e14cf57dfc0b
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Sun Apr 27 11:39:14 -0700 2008 | [dustin] |
| |
Emakefile | Sun Apr 27 11:39:14 -0700 2008 | [dustin] |
| |
License.txt | Sun May 04 03:49:43 -0700 2008 | [tim] |
| |
Makefile | Sun Apr 27 11:39:14 -0700 2008 | [dustin] |
| |
README.txt | Sun May 04 03:45:39 -0700 2008 | [tim] |
| |
src/ | Sun May 04 03:49:43 -0700 2008 | [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.




