> Looks almost okay. The URL (given to a client) can start with any of the
> following,
>
> tp://
> tps://
> http://
> https://
> tphttp://
> tphttps://
Cool - can we say http and https are deprecated?
> > Is there any other transport protocols?
>
> Not at the moment.
Good - The tphttp one is ugly enough ;-)
> > The (.*) is there for http only I assume? (I assume it is needed for http)
>
> The (.*) is the "game name". On servers which have only one game it can
> be ignored. On servers which have multiple games it should be appended
> to the username.
That doesn't make sense?
If the game is 'testgame' my url is:
tp://[EMAIL PROTECTED]:[EMAIL PROTECTED]:protocol/testgame
For http servers I want the trailing data to be for the HTTP request to
get the correct location: So I don't have to only run a TP server on my
root. eg
tphttp://server/path/to/tpserver
Also how does http authentication work along with tp authentication?
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.
> > How does one specify a game to join if the server has support for
> > multiple games?
>
> See above.
Once again - this needs to be better i think. And is it in @ or
trailing / format?
> > Should http games be specified as tp+http or similar?
>
> Do you know if tp+http is a valid name, it would be better then tphttp
> which we currently use.
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.
> > Also, is it worthwhile starting the scheme registration process for the
> > tp (and tp+http) scheme?
>
> 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-guidelines-01.txt
> The tpclient-pywx registers for tp, tps, tphttp and tphttps links in
> Windows and Gnome.
Shall look at registration for similar in my client as well.
> > And can this be put up on the website, or if it is there, linked from
> > the protocol doc ;-)
>
> It'll go in the protocol4 document.
Cool.
Regards,
nash
[1] Having said that I only recently (12 months) became aware of it, and
I can't find a definitive reference to say 'this is the way to do'. The
best examples I've seen are git clients which use git+ssh: or git+http:
for git over other protocols.
[2] There are two protocols which use the 'dns' scheme.
_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
