You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ionel GARDAIS <ig...@yahoo.fr> on 2006/09/21 15:25:46 UTC
single exit point for svnserve
Hi,
What are the pros and cons for adding a method like "svn_shutdown_hook
()" that will be called when svnserve is running as a daemon or a
service and the process is beeing asked to quit ?
This question is not innocent : it's for getting a single piece of
code to deregister Bonjour service.
Thanks,
Ionel
___________________________________________________________________________
D�couvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/R�ponses pour partager vos connaissances, vos opinions et vos exp�riences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: single exit point for svnserve
Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Thu, Sep 21, 2006 at 05:25:46PM +0200, Ionel GARDAIS wrote:
> What are the pros and cons for adding a method like "svn_shutdown_hook
> ()" that will be called when svnserve is running as a daemon or a
> service and the process is beeing asked to quit ?
>
I thought that we had already added something similar when we added
support for svnserve running as a Windows service?
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: single exit point for svnserve
Posted by Peter Samuelson <pe...@p12n.org>.
[Kevin Greiner]
> We already are able to move svnserve from one server to another
> without telling end-users. We just move the service to another server
> and change the DNS entry (svn.company.com) to point to the new IP
> address.
>
> I've been attempting to follow this bonjour conversation but don't
> understand the benefits. Can you clarify?
One big point of zeroconf _in general_ is to allow random users on a
network to "browse" services available without already knowing any
hard-coded addresses. A user could fire up a svn client and hit
'browse for servers' and get a list of the 3 svnserve processes which
have helpfully been labeled 'development', 'anonsvn' and 'test-svn150'
(hey, who knows, some companies might try to _test_ a new major svn
version before rolling it out). Future directions would allow browsing
not only by the label for svnserve but by the repository name - this is
what the others are discussing now.
Think of it as NetBIOS or Appletalk browsing, without the pain of
NetBIOS or Appletalk. This is what allows a Mac OS "Chooser" applet to
present a pile of printer icons for all the printers available across
your local network, so that you can just pick a printer based on its
name and description, rather than knowing its exact address in advance.
DNS aliases work fine when there is a well-known DNS name that everyone
will guess, like 'www.example.com' for a company web site. They don't
work so well for "show all printers or Subversion servers being made
available to me on this LAN". And they don't work if there might be
multiple services of the same type hosted on the same machine, which
could happen for svnserve.
Re: single exit point for svnserve
Posted by Kevin Greiner <gr...@gmail.com>.
On 9/22/06, Ionel GARDAIS <ig...@yahoo.fr> wrote:
>
> Isn't it because a user does not care about where the server is that
> the server itself should use zeroconf (at least for internal-running
> servers) ?
> Sysadmin guys could migrate svnserve from servers to servers without
> telling end-users.
>
We already are able to move svnserve from one server to another without
telling end-users. We just move the service to another server and change the
DNS entry (svn.company.com) to point to the new IP address.
I've been attempting to follow this bonjour conversation but don't
understand the benefits. Can you clarify?
Re: single exit point for svnserve
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 9/22/06, Ionel GARDAIS <ig...@yahoo.fr> wrote:
> OK.
> Quickly analysing what options are available, a solution is to allow
> the user to specify a file used for service name <-> repository path
> mapping.
> Using access files and svnserve.conf files suppose that the server
> already know where repositories are.
I suspect that sooner or later we're going to have to give svnserve a
config file (even an optional one), perhaps specified via a command
line option:
svnserve --config /path/to/my/config
That could include a list of what should be advertised over zeroconf,
among other things. I imagine that for some options (passwd file,
authz file, etc) you might want the per-repos config to override the
global one.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: single exit point for svnserve
Posted by Ionel GARDAIS <ig...@yahoo.fr>.
OK.
Quickly analysing what options are available, a solution is to allow
the user to specify a file used for service name <-> repository path
mapping.
Using access files and svnserve.conf files suppose that the server
already know where repositories are.
Ionel
Le 22 sept. 06 à 17:22, Garrett Rooney a écrit :
> On 9/22/06, Ionel GARDAIS <ig...@yahoo.fr> wrote:
>> Isn't it because a user does not care about where the server is that
>> the server itself should use zeroconf (at least for internal-running
>> servers) ?
>> Sysadmin guys could migrate svnserve from servers to servers without
>> telling end-users.
>
> Sure, and having zeroconf advertise the location of the server is
> certainly helpful, but the user still has to go talk to someone to
> find out the path of the repos and the path of the project within the
> repos. It just seems like you're only solving part of the "How do I
> check out the code to project X" problem, when it should be possible
> to solve more of it.
>
> -garrett
___________________________________________________________________________
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: single exit point for svnserve
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 9/22/06, Ionel GARDAIS <ig...@yahoo.fr> wrote:
> Isn't it because a user does not care about where the server is that
> the server itself should use zeroconf (at least for internal-running
> servers) ?
> Sysadmin guys could migrate svnserve from servers to servers without
> telling end-users.
Sure, and having zeroconf advertise the location of the server is
certainly helpful, but the user still has to go talk to someone to
find out the path of the repos and the path of the project within the
repos. It just seems like you're only solving part of the "How do I
check out the code to project X" problem, when it should be possible
to solve more of it.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: single exit point for svnserve
Posted by Ionel GARDAIS <ig...@yahoo.fr>.
Isn't it because a user does not care about where the server is that
the server itself should use zeroconf (at least for internal-running
servers) ?
Sysadmin guys could migrate svnserve from servers to servers without
telling end-users.
Ionel
Le 22 sept. 06 à 17:12, Garrett Rooney a écrit :
> On 9/22/06, Ionel GARDAIS <ig...@yahoo.fr> wrote:
>> I will only advertise the IP/port of the listening svnserve process
>> along with an user-defined service name.
>> The users *must* know the full repository access path to get into it.
>
> See, to me that seems almost entirely useless. If you're going to
> advertise over zeroconf, I'd expect you to want to advertise on a
> per-project bases, which means either per-repository or per-directory
> within a repository. A user doesn't really care where the server is,
> they care where they can check out the code to project $WHATVEVER.
>
> -garrett
___________________________________________________________________________
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: single exit point for svnserve
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 9/22/06, Ionel GARDAIS <ig...@yahoo.fr> wrote:
> I will only advertise the IP/port of the listening svnserve process
> along with an user-defined service name.
> The users *must* know the full repository access path to get into it.
See, to me that seems almost entirely useless. If you're going to
advertise over zeroconf, I'd expect you to want to advertise on a
per-project bases, which means either per-repository or per-directory
within a repository. A user doesn't really care where the server is,
they care where they can check out the code to project $WHATVEVER.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: single exit point for svnserve
Posted by Ionel GARDAIS <ig...@yahoo.fr>.
I will only advertise the IP/port of the listening svnserve process
along with an user-defined service name.
The users *must* know the full repository access path to get into it.
Ionel
Le 22 sept. 06 à 15:59, Garrett Rooney a écrit :
> On 9/21/06, Ionel GARDAIS <ig...@yahoo.fr> wrote:
>> Hi,
>>
>> What are the pros and cons for adding a method like
>> "svn_shutdown_hook
>> ()" that will be called when svnserve is running as a daemon or a
>> service and the process is beeing asked to quit ?
>>
>> This question is not innocent : it's for getting a single piece of
>> code to deregister Bonjour service.
>
> If you need such a thing as part of something you're implementing, I'd
> suggest just adding it as part of that patch. If it later turns out
> to be something generically useful, we can always abstract it out.
>
> One thing to keep in mind though, if you're looking to advertise
> svnserve's repositories over zeroconf, you'll have a bit of trouble,
> because svnserve doesn't know at startup what repositories it's
> serving, it just has a root directory, and any repository under that
> directory can be served up.
>
> -garrett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
___________________________________________________________________________
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: single exit point for svnserve
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 9/21/06, Ionel GARDAIS <ig...@yahoo.fr> wrote:
> Hi,
>
> What are the pros and cons for adding a method like "svn_shutdown_hook
> ()" that will be called when svnserve is running as a daemon or a
> service and the process is beeing asked to quit ?
>
> This question is not innocent : it's for getting a single piece of
> code to deregister Bonjour service.
If you need such a thing as part of something you're implementing, I'd
suggest just adding it as part of that patch. If it later turns out
to be something generically useful, we can always abstract it out.
One thing to keep in mind though, if you're looking to advertise
svnserve's repositories over zeroconf, you'll have a bit of trouble,
because svnserve doesn't know at startup what repositories it's
serving, it just has a root directory, and any repository under that
directory can be served up.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org