THOUGHTS in resque_stuck_queue-0.0.1 vs THOUGHTS in resque_stuck_queue-0.0.2

@@ -17,5 +17,15 @@
 reproduce the error and integrate test like that
 
 ## TODOS
 
 verify @config options, raise if no handler, etc.
+
+- use locks to only notify/trigger once in case this is used in a server-cluster type environment adn you only want the handler triggered once
+
+- resque in stuck (t state process) SIGSTOP sticks up the checker thread?
+  or if not running
+
+- ensure it only runs from the server box and not the resque box??
+  (the deploy restarts the server but not resque workers)
+
+