URLs are used to identify and locate various resources in Alloverse. This document should be a full list of such URLs and their format.
There is currently one format for locating an alloplace server:
host: Hostname or IP of machine that is running the
port: This is the enet UDP endpoint for the listen socket. Optional: default value is 21337.
Such an URL should be fed into
alloclient_connect or its high-level equivalents, and
allonet will take care of parsing and connecting to the server at that URL.
The downside of this scheme is that it doesn’t allow for virtual hosting: with the same domain name for the same IP, you’ll end up at the same placeserv unless you include a custom port in the URL, which is ugly.
One solution is to use a HTTPS gateway which returns the real alloplace URL given a URL of this form:
Another solution is to have a “load balancer” allplace socket which forwards to an internal instance. This solution can use the original
alloplace:// url schema.
Launching an alloapp from a URL is not implemented yet. Here’s how I imagine it working:
… with HTTP headers for user identity and alloplace to connect to.
This is a HTTPS endpoint which is basically a “CGI launcher”. Upon POST, it’ll launch an instance of the app and connect it to the requested alloplace.