[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] url schemes

From: Timothy Brownawell
Subject: Re: [Monotone-devel] url schemes
Date: Sun, 30 Mar 2008 13:09:42 -0500

On Tue, 2008-03-25 at 12:20 +0100, Markus Schiltknecht wrote:
> Hi,
> Timothy Brownawell wrote:
> > push/pull/sync are not GET/PUT/DELETE operations, they need a lot of
> > negotiation to find out what to send. They cannot be directly supported
> > by dumb servers, you need a smart client with the necessary logic to
> > break them down into simpler parts.
> I fully agree. And for nuskool, those simpler parts are http GET requests.
> > Simple URLs to specify what to sync against are very convenient, but why
> > should they be force-fit into a scheme which is not designed for that
> > sort of interactive operation?
> To ensure that the URL scheme survives long enough to be of relevance. 
> To me, it just doesn't make sense to have the following URLs in parallel:
>   * mtn://
>   *
> I think that just leads to unnecessary confusion for no good reason.

When is nuskool expected to land? Your suggested URL style won't work
for file and ssh sync without changes to netsync, so it's not currently
implementable (I'm also not sure how it's intended to handle branch
patterns, as opposed to only branch names). If nuskool is expected to
land Real Soon I suppose I could back out my changes, but if it's going
to take as long to be ready as various other features have then that's
probably not the best.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]