Re: Confusing terminology between usher and monotone and proposed change

On Tue, May 10, 2011 at 09:09:15AM +0200, Richard Levitte wrote:
> 
> With my idea (just for the sake of being explicit), the following:
> 
>     server "newpub"
>     local "--confdir" "/home/levitte/usher.projects/newpub" "-d" "/home/levitte/usher.projects/newpub/database.mtn" "--no-standard-rcfiles" "--rcfile" "/home/levitte/usher.projects/newpub/monotonerc" "--timestamps" "--ticker=dot"
> 
> would be replaced with:
> 
>     path "newpub"
>     local "--confdir" "/home/levitte/usher.projects/newpub" "-d" "/home/levitte/usher.projects/newpub/database.mtn" "--no-standard-rcfiles" "--rcfile" "/home/levitte/usher.projects/newpub/monotonerc" "--timestamps" "--ticker=dot"
> 
> In human terms, the former would be expressed "this is the server
> named 'newpub', and local indicates how to start it."  The latter
> would be "the path 'newpub' is served with a monotone started with the
> arguments given by local."
> 
> hendrik> But the word "path" is in common usage to a sequence of
> hendrik> directory names separated by slashes, possibly ending in a
> hendrik> file name.
> 
> The word "path" has been expanded, especially if we speak in URI
> terms, to something of a structured notation to reach a specific
> resource within a specific realm.  That's exactly the way PATH is
> used in mtn://HOST/PATH?PATTERN .

This answers my objection to the word "path".  Framing the ter+minology 
this way removes the confusin.

-- hendrik