Parse odamex:// protocol URIs
In order to support Rich Internet Application (RIA) interaction, it is necessary to have some method of instantiating odamex application services. One convenient way to do this is via a URI. Currently, when one launches odamex via this URI method, odamex receives one argument that ends up being the entire URI itself, i.e.: odamex://odamex.org:10666/?+fullscreen=0 The above becomes argv[0] and argc is 1. Odamex should parse these into a form it can digest. Likewise this could be done with launching odasrv: odasrv:///?+hostname=abc def&port=10669 (third slash after colon to match above where location would be).
r751 client interprets argv[0] of the format "odamex://odamex.org:10666/"
Tested r801, there's no feedback in the console and client just starts up as if nothing was passed to it.
what is your test?
Two fold, using my existing registry setup that passes the url to odamex.exe as the only argument and manually invoking it by simply doing: odamex.exe odamex://odamex.org:10666 Which is the same thing that the uri passing from the browser does.
that would be passed as argv[1], not argv[0] argv[0] = "odamex.exe" argv[1] = "odamex://odamex.org:10666"
the current version of the client also looks for the terminating '/'
r806 parses argv[1] instead of argv[0] and does not require the extra slash
It does in fact do this. Now, if it could then look for /? and parse everything after it as a set of args separated by & it'd be complete.