SvnBridge & Multiply Servers

Mar 26, 2008 at 8:21 PM
Hi guys,
I have spent most of the day working on supporting multiply servers.
The infrastructure is there, but I haven't exposed it in the UI yet.
The functionality is actually different from the method that we have used so far.
With the new approach, if you want to checkout the SvnBridge code, you would do:\

svn checkout http://localhost:8081/tfs03.codeplex.com/SvnBridge

Note the tfs03.codeplex.com in the URL ? This is how we specify which server we use.
If we want to specify a port, we can use:

svn checkout http://localhost:8081/my-team-system-server:8080/MyProject

SvnBridge will also auto detect http and https, so you don't have to worry about this.

Thoughts?
I am considering making this the default in the local version.
Mar 26, 2008 at 9:34 PM
Edited Mar 27, 2008 at 12:00 AM
Why not utilize DNS on the user's system so that instead of using localhost they can use the actual address? It would eliminate such a strange URL syntax.

I would prefer something like:

svn checkout http://svnbridge.tfs03.codeplex.com:8080/SvnBridge

You could, for example, append 'svnbridge' to the front of the actual URL (to avoid overwriting the valid entry in DNS)
Mar 27, 2008 at 3:45 AM
I'm not sure I understand how we would "utilize DNS on the user's system"? Would you add entries to the hosts file, or something else?
Mar 27, 2008 at 2:51 PM
Well I'm not a web developer or a web guru for that matter, so I may be sounding like a complete idiot. All I know are the basics. I know that each computer has a DNS table of some sort that maps names to IP addresses. Basically, I'm saying try to use that if you can in order to clean up the URL a bit (as it looks very mangled, messy, and hard to understand). I apologize if I'm being confusing, but again I'm not a network guru so I'm not familiar with the correct terminology.
Mar 27, 2008 at 3:11 PM
Edited Mar 27, 2008 at 3:12 PM
delete this please
Mar 27, 2008 at 7:13 PM
The problem with doing that is that I would need to interfere directly into the way the OS networking works
This is not for the faint of heart, and most users would find it unacceptable that a program would do that. (Basically, it would turn SvnBridge into a firewall).
Mar 27, 2008 at 9:08 PM
Then I guess your original proposal is going to be fine. However, I would expect you to make a combo-box drop down for URLs so that I don't constantly have to type in the address when I swap servers. I had requested this feature in a separate work item a while back, but I feel that when you introduce this new complex URL design that you should at the same time provide a combo box that saves a list of, for example, the last 20 entered URLs (Note that it would also need to remember the forwarding port as well, which is currently in a separate edit control)
Mar 27, 2008 at 9:35 PM
This feature supersede this request, since now you don't need to deal with url per server.
You use the server from request mode, and just put the team server url in the co url.
Mar 27, 2008 at 10:57 PM
OH, okay. I misunderstood then. You're right, no need for a combo box anymore! I like this feature; you should implement it (now that I understand how it works I like it a lot)
Mar 28, 2008 at 2:57 AM
Yes, it is online and working now.
Mar 12, 2009 at 5:04 PM
So, do I understand correctly... am I headed down the right path? Have several TFS sites to connect to from TortiseSVN, for example a project bar at tfs01.foo.com:9090.  If I setup SVNBridge to listen on port 18080, I do not need to muck with 'proxy' settings(?) and the URL I want to use in TortiseSVN would be http://localhost:18080/tfs01.foo.com:9090/bar? This has not worked for me, so far. I am running a copy of SVNBridge that has a date of December 2008 (have not found where a version number can be displayed... no "About" option)... is this a feature of only newer builds? When would I want to use 'proxy' settings (I am also a brand new user...)?