I think it would be a cool addition if the BYOND pager/webclient were to translate hostnames without port numbers by doing a DNS lookup on the hostname for the "byond" service, much in the same way that Minecraft and a few other game servers do.
It would then be possible to post links such as "byond://play.mygame.com" and have your host worry about the port number.
ID:1870107
Jun 10 2015, 10:23 am
|
|||||||
| |||||||
Jun 10 2015, 10:44 am
|
|
This is effectively what the byond://BYOND.world.nnn format does, although I agree it'd be nice to do that for names rather than numerical IDs. However I don't see how the webclient could ever handle that.
|
In response to Lummox JR
|
|
Lummox JR wrote:
However I don't see how the webclient could ever handle that. The webclient operates from byond.com, so technically you could change the URL the player connects to by doing a lookup if the corresponding IP address couldn't be found. |
Well yes, our page on the site already can look up that world ID that way, and Tom and I envisioned being able to setup a name. But that won't apply to things like resources.
|
In response to Lummox JR
|
|
Lummox JR wrote:
Well yes, our page on the site already can look up that world ID that way, and Tom and I envisioned being able to setup a name. But that won't apply to things like resources. What do you mean? If you redirect the iframe/client to the right hostname+port (after performing the lookup) doesn't it all fall into place? I'm referring to when you connect to http://www.byond.com/play/play.myawesomegame.com and then sending a 301 redirect to http://www.byond.com/play/123.123.123.123:5000 as the SRV record specifies. |
A lot depends on how the browser cache operates. Does it cache by the original URL or the redirect? I believe in most cases it caches by the redirected URL.
|