proposed URL change

We have various customers who are securing their use of BK via ssh.  When
we made up the URL format we didn't anticipate needing port numbers in
the ssh urls (our bad, sorry about that).

We could create a new url like ssh+port://<user>@<host>:<port>:<pathname>
or something like that but that is really ugly.

As it turns out, we already support the following:

    ssh://<user>@<host>/<pathname>

as well as the documented:

    ssh://<user>@<host>:<pathname>

The proposed change, for all url://host:pathname forms, is to drop the use
of ":" and replace it with "/".  

That's a fairly visible interface change.  What we could do to ease the
transition is look at what follows a ":" and if it looks like a number then
we treat it as a port and move forward and otherwise we treat it as we
used to do.  That's probably the right answer.  In other words:

    ssh://[email protected]:LMbench would be viewed as 
    user=lm
    host=bitmover.com
    path=./LMbench2
    port=default ssh port

but ssh://[email protected]:1234/LMbench2
    user=lm
    host=bitmover.com
    path=./LMbench2
    port=1234

The only people who would get bit by that are those people who have 
repositories which are named by all numbers, no other chars.  That 
seems pretty safe.

Comments?
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
_______________________________________________
Bitkeeper-users mailing list
[email protected]
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.