[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN Proxy

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-06-07 10:41:20 CEST

Ramprasad Venkata Inala wrote:
> Hi,
> I want to write a proxy for SVN ( for SVN protocol )so that it passes
> through our versioning system. For the same I need to know the SVN
> protocol, which I understood from the protocol document placed in the
> SVN sources. There is some hiccup while handshaking with the client. Let
> me explain in detail what I do.
> When a client ( using a subclipse ) tries to connect to the SVN proxy(
> a socket server program written in java ) the proxy accepts the
> connection and spawns a new thread that will handle further the requests
> for this client, so each client will have a thread that would handle the
> streams. When server socket accepts the client request it sends back
> response in the format specified below.

> ( success ( 1 2 ( ANONYMOUS ) ( edit-pipeline ) ) )


> ( 2 ANONYMOUS ( ) ( ) )

What is this?? I do not see this in either the protocol document or in
captured traces of network traffic.

> The client responds back with the below response
> ( 2 ( edit-pipeline ) 28:svn:///d:/svnrep/SVNProtocol )


> Then the proxy sends a message in this format again to the client
> ( ( ( 31:d:/svnrep/SVNProtocol ) ) ( ANONYMOUS ( ) ) )

Again, what is this?? I do not see this in either the protocol document or
in captured traces of network traffic.

> Then the problem starts here again when the client responds back then it
> tries to open up another socket rather sending requests on the same
> stream which is a diversion from the connection establishment.

I suspect the client is giving up faced with the weird responses you are
giving it, and re-trying.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 7 10:45:53 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.