Updated feature ideas, moving my stuff to http://dbalatero.lighthouse…

…app.com/projects/31581-queue_stick

design_docs/FEATURE_IDEAS

@@ -8,7 +8,7 @@ DONE * Command-line flags for:
 DONE * Provides easy interface for implementing a queue worker.
   * process(record) ?
   * recover ?
-* (maybe later) Failure emails for given SQS message?
+NOT GOING TO DO * (maybe later) Failure emails for given SQS message?
 DONE * Should never remove a message from the queue if it can't
        successfully process it.
 DONE * Should allow people to test their queue code easily.
@@ -18,11 +18,11 @@ Push:
 
 DONE (7e47dde) * adding a convenience method for accessing counters within a worker
 DONE (bab952e) * running N threads of workers
-* displaying counters / runtime information on the embedded Sinatra app
+TICKET * displaying counters / runtime information on the embedded Sinatra app
 NOT GOING TO DO * creating a binary to run a worker (queue_stick <my_worker_rb_file> --port 4999, for example)
-* generator for making a skeleton for a queue worker
+TICKET * generator for making a skeleton for a queue worker
 DONE * moving the SQS-specific class methods out of Worker into a SQSWorker subclass
-* implement SQS get/delete methods
+TICKET * implement SQS get/delete methods
 
 Possible DSL
 ---------------