/xcraft/infrastructure/index.html A land needs chiefs, roads, horses, dialects and more in order to trade between species The beginning of wisdom is the statement ‘I do not know.’ The person who cannot make that statement is one who will never learn anything. And I have prided myself on my ability to learn. – Thrall The infrastructure is organized by a network of Xcraft servers where it’s possible to have dedicated work for each node. Hugo en-us /xcraft/infrastructure/client/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/infrastructure/client/index.html There are two levels of accesses to the buses of an Xcraft server. There is the low level (for Orcs), and it’s the Xcraft API. For the Goblins, you will use an higher level of API based on the Quest context. Xcraft level? Orcs? Goblins level? But what the hell? – Human without Mana The Goblins live in a land governed by the Orcs… Okay, I’ve lost you, sorry.. The Xcraft’s name is a nod to the WarCraft game, but it’s not just that. /xcraft/infrastructure/messages/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/infrastructure/messages/index.html Serializer The Xcraft messages (by command like by event) know how to send Immutable.js objects (and Shredder) as far as these objects are provided correctly. In order to be serializable, it must be compliant with one of the following points: As value of msg.data As value in an array provided in msg.data As value in an object provided in msg.data where msg is the Xcraft envelop and data the user payload /xcraft/infrastructure/commands/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/infrastructure/commands/index.html /xcraft/infrastructure/events/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/infrastructure/events/index.html How to use This section will explain a lot of details about the events and subscriptions mechanisms. It uses only the Goblin API. But note that it’s possible to use the Xcraft API as well and in this case, you can find some informations at this section. Subscribe When subscribing to a topic for events, a simple syntax can be used in order to group multiple events to one subscription and without the use of regexes. /xcraft/infrastructure/backends/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/infrastructure/backends/index.html Use horses when traveling in the lands, but prefer more faster and appropriate transports when talking to your neighbours There are two backends in the transport layer. The first one is named EE and it’s based on the EventEmitter of nodejs. The second one is named Axon and implements a particular protocol on TCP/IP. The base idea is simple. A message where the destination is in the same process, uses the EE backend. /xcraft/infrastructure/server/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/infrastructure/server/index.html /xcraft/infrastructure/routing/index.html Mon, 01 Jan 0001 00:00:00 +0000 /xcraft/infrastructure/routing/index.html Multicasting with Xcraft By multicasting we talk about the ways where the events must follow from a sender to one (unicast) or multiple (multicast) receivers. The original implementation was using only the broadcast. For performances and security reasons, the multicast was necessary. In order to achieve this goal, we have implemented a complete mechanic in the router stuff (see xcraft-core-transport module). To multicast we must know which are the clients and where they are.