Runnables!

[IDragonfire]

Proper Task-based scheduling in Sponge

I’d like to see proper task-based scheduling in Sponge. Tasks are a super powerful abstractions on top of a scheduler for defining work that needs to be done in the future. Bukkit had primitive support for tasks, but it lacked a continuation mechanism for invoking another task at the completion of a first. Where task continuations become particularly powerful is when switching threads to do work outside of the game loop and then returning control to the game loop to apply the results. Here is a…

Formal threading model for the API

The MC server has basically a single “main” thread and lots of other minor threads. Almost all events occur on the main thread (except those that don’t) and similarly almost all methods in the API had to be called from the main thread (again except those that didn’t). In future versions, worlds might be handled on their own thread. Glowstone already does this and there has been suggestions that MC might go that way too. If we say that calling any API method from inside an event handler is al…

Using an Rx-inspired event system

That’s a pretty cool idea, but it’s not what I was thinking. The API seems a bit clouded. I should explain a bit more. By default the observable is ‘executed’ using the game loop scheduler. This schedules the observable to compute in the same tick, and is a good behavior for most cases. There should be a Scheduler interface. One for the game loop(e.g. server.scheduler.loop), one for ‘asynchronous’ computation server.scheduler.async that is outside the game loop, and finally a delayed game loop…