From 56fc74118e97b069aac14c94b6216b334497098b Mon Sep 17 00:00:00 2001 From: Vincent Driessen Date: Tue, 15 Nov 2011 00:22:24 +0100 Subject: [PATCH] Get rid of the formal definition. We're not a lawyer agency here. --- README.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/README.md b/README.md index 854e16f..7b42651 100644 --- a/README.md +++ b/README.md @@ -8,16 +8,6 @@ queue provider. # Putting jobs on queues -Some terminology before we get started: - -* *Queues* are queues, in the computer science way. Technically, they are - Redis lists where work is `rpush`'ed on and `lpop`'ed from. -* *Jobs* are a definitions of work that can be carried out by a different - processes. Technically, they are just plain old Python function calls, with - arguments and return values and the like. -* *Workers* are processes that pop off work from queues and start - executing them. They report back return values or exceptions. - To put work on queues, tag a Python function call as a job, like so: @job('default')