CraftBukkit/Spigot b1d40801aa Rewrite scheduler. Fixes BUKKIT-1831, and BUKKIT-845 ... The new scheduler uses a non-blocking methodology. Combining volatile references to make a linked reference chain, with the atomic reference handling the tail, tasks are queued without waiting for locks. The main thread will no longer limit the length of time spend for scheduled tasks, but no task will run twice in the same tick. Scheduling a new task inside of a synchronous task will always run the new task during the same tick, assuming there is no supplied delay > 0. Asynchronous tasks are now run using a thread pool. Any thread-local implemenation should now account for threads being reused between executions. Race conditions were carefully examined and the order of logic is now very important. Each task is placed in a secondary collection before removal from primary collections. Thus, by reading tasks from the collections in the same order they travel, it retains state-safety. This does make modifications less responsive in some situations, as the task may be transitioning before the modifier accesses it. This cost outweighs the requirement to synchronize on the scheduler; previously any conflict would be first-come-first-serve, with the main thread backing out arbitrarily. By: Wesley Wolfe <weswolf@aol.com>		2012-08-14 06:09:51 -05:00
..
main	Rewrite scheduler. Fixes BUKKIT-1831, and BUKKIT-845	2012-08-14 06:09:51 -05:00
test/java/org/bukkit	Add test for WorldType's	2012-08-02 09:10:15 -05:00