Re:SVN REPOS: WAS: SVN API

Ahh. Is that what this is all about.

Consider this.

You get a standardized http server that you can install along side subversion, with a
standardized port. Or alternatively in a standardized location under apache. Or a
standardized cgi you can alway check for.

Add in a few standardized challenge-response protocols for access and you can
control whether the data is transmitted or not.

This is what the other guy was asking for - where can I go to find all the repositories
that have been registered.

If you keep doing it differently on every box, the protocol becomes impossible to
follow.

If you give everyone widget, people can use it for many many different uses.

Secondly - a static html page helps people. What good is HTML to a machine.

What I'm talking about would also speak XML on request instead.

Think web services.

So I guess I'm proposing figuring out a way to automate repository location
management as a web service/http request (for people).

Why have a static page when you have to maintain that page. Why not delegate that
activity to the users of your metarepository?

And if I were to use Subversion to automatically maintain said 'page' which may or
may not exist in actuality, I can track the progression and usage of repositories within
an organization - another plus for bean counters who like to know if something is
actually being used.

And lastly, were there a centralized way as an addon to subversion, you would lose
less information and have less duplication of effort.

Isn't this what the other guy was going on and on about?

I'm not talking about reinventing the wheel. I say we have the tools within subversion
to standardize this set up in a way that's flexible and usable for everyone - with a few
addon tools of course. But we already allow python bindings, so addons are not new
to us.

I mean, seriously, I thought the only problem was manpower.

Am I missing the boat here?

Shamim Islam
BA BS

Max Bowsher (maxb@ukf.net) wrote:
>
>Files wrote:
>> Did everyone like up and decide that no one wants this? I thought I was
>> just hearing that no one thought the main subversion developers should
>> work on this. But that if someone wanted to work on it, it was swell.
>
>I think most people (including me) don't understand what benefit your
>proposed project brings over a simple static HTML page listing repositories.
>
>Max.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Sep 13 16:28:22 2003