> > > > Cool - can we say http and https are deprecated? > > Yes. Also note that as of tp04, tps will not be necessary as the tp port can > support an ssl/tls filter.
The library I use for socket connections needs to have SSL set at initial connection. So a 's' hint is useful (else I need to drpo the socket, and reconnect). > I think it should be tp://nash:[EMAIL PROTECTED]:port/gameshortname. Also > note > that putting the password in the uri (partially on the command line) is > highly discouraged. It is however fine for configuration files. Yes password on command line is inadvisable - especially on a multi-user system ;-) /me needs to add support for 'password' files. > The tphttp and tphttps schemes are to allow using http proxy to escape tight > networks. As tp is tunnelled over it, I don't think it's necessary to allow > having the server not as the root. Cool. > > Note that URL - two '@' and two ':' - both optional is a nightmare to > > parse. I think it can't be ambiguous, but I can't prove it. > > One '@' and two ':' are in the standard for URIs. You don't really need more > than that. With the game name at the end - it works fine. > I think it should be trailing. (I note that since tpserver-cpp only runs a > single game at a time, I don't really care). Implemented as such. As aside the metaserver should probably be a little more aggresive escaping characters in game names... eg ' in "Lee's Dev Game" > > tp+http is a valid name. My understanding is[1] that it is the correct > > (but not only) way of saying tp over http protocol (however you > > generally register tp+http). + is a valid character for schemes. > > Good point, but it's not exactly correct. The git+http example is still pure > http, with the path expected to be a git repo (unless it does something > special, like webdav). Git does webdav quite happily. > > > scheme registration process? > > > > You can register schemes so no-one else can use it - avoids the 'dns' > > issue[2]. Probably not ready for TP yet... but hopefully will one day. > > Info is available in a number of places: > > http://ietfreport.isoc.org/all-ids/draft-hansen-2717bis-2718bis-uri-guideli > >nes-01.txt > > Maybe. Maybe we should register port 6923 with IANA as well. 6923 is probably more important. Regards, nash _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
