Why? Users want to be able to send a simple POST request to broadcast a global message to all connected clients. This is useful for integrating WorldQL-powered services with external systems. HTTP is WAY easier to use than websockets and doesn't require any additional client libraries.

What? WorldQL should run an HTTP server in addition to ZeroMQ and WebSocket listeners. There are a variety of options that fit into the tokio event loop, but hyper seems to be the most popular. It should listen for incoming messages on a POST /global_message endpoint which accepts the following request

{
    // HTTP headers. Use basic auth token defined by a new WQL_HTTP_AUTH_TOKEN environment variable
    headers: {'Authorization': 'Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ'},
    // request payload. Sent as a JSON string.
    data: {'instruction': 'GlobalMessage', 'parameter': 'ExampleIntegrationRPC', 'world': '@global'}
}

The server should process this request, marshal the data into an internal Message struct, and process the GlobalMessage.

The scope of this mission is very limited: for now, we only need GlobalMessage support and we're fine with the most basic auth possible. Additionally, the /global_message endpoint does not have to return any meaningful data to the requester. A simple 200 response with no body will suffice.

Sometimes databases fails, and WorldQL clients must switch to another server. To maintain consistency, servers must synchonize changes.

Is WorldQL supporting that now?

Hello, I have readed the code corresponding to records stored in database. If i am correct you are using postgresql to store it. I think you can optimize the region management by using posgis. http://postgis.net/workshops/postgis-intro/indexing.html

The idea is to create bounding box based on xmin, xmax, ymin, ymax of each area. By using postgis you can create geographical index by example an quadtree. An other option can be to store points objects directly in records and create an rtree index to easily get records or entity by distance. This option can maybe not really useful on mammoth by can be usable in other cases and allow more complex features.

Your project is so interesting that i have started reading rust for the first time.