Removed javadoc that is not relevant or correct
Added a third type of limiter...this one is just for SimpleScheduler's.  In case you don't need or want the entire PrioritySchedulerInterface, this allows you to use a limiter, and still be able to schedule (and not just be forced to use an executor)
Step in reducing code duplication between these two limiters
Added a simple getter here
Name the Clock thread and cleanup the code slightly
Working on issue #33, this reduces some of the code duplication and cleans some other things up (also has some minor performance improvements for the right situations)
Lot more code duplication reduction for issue #33
Fixes for checkstyle
Just moving this interface location to match the simple one
Simple argument re-ordering
No need to signal all here
Move these constructors higher like you would expect them to be
This resolves #34.  The solution is to track how far behind high priority tasks are, and to artifically slow down low priority tasks as high priority tasks get backed up.  This incurrs almost no overhead for high priority tasks, and the overhead for low priority tasks also remains very minimal.
Removed comment that does not help anything
Prevent a possible overflow
Just simpler to make these zero, should not be functionally any different
In very slow systems we may not wake up fast enough to notice the 100ms gap, so just increasing this to prevent an exception which may not be true
Some small unit test additions
Removed unused class from unit test
This does not need to be volatile, it is guarded by UPDATE_LOCK