jbilcke
commented
9 years ago still need to be done
I think we need something closer to a message board and realtime issue tracker rather than a message queue, because we want the ability to run thousand of queues in parallel, each with different priorities, and also we want some messages to stay without time limit, like a loop
maybe it will be something like this: https://github.com/autogica/gunfire/blob/master/src/client/utils.coffee#L318
it is a prototype of an issue/message system that uses multiples indexes and sorts to dispatch messages. For now, it is oriented toward a simple request/proposal model, and uses a vocabulary inspired by economy:
an entity (a real human player, or a robot) in the game needs something, for instance a laser weapon, or a drone, and is ready to "pay" for it (using energy, for instance collected by mining).
It posts the issue, under a given topic (or keywords) and other entity that provides services or products will watch the topic, and answer to the original entity with an offer. If both parties agree then this is a deal. Tho whole thing should take less than a few asynchronous function calls.
Asynchronous communication is necessary because it allows us to introduce a few things in the model:
- security and money / bank checks can be done during this time
- "long calls" can be made possible (ie. calls to another server or instance of the game)
- entities have more time to thinks of what to do
- this creates competitions between entities: multiple entites can propose a deal
- the faster will win more bids, this leaves place to evolution and optimizations
- some entities may provide cheap or free services, for some use cases
this kind of call:
var foo = window.app.assets['atgc-part-tactical-javelot'].launch()is dangerous, needs dependencies to be loaded in the correct order, can be broken during migration and upgrades
it should be replaced with an asynchronous, message passing system like an event-emitter or actor system.