Actually I don't need to know any of that (unless you guys put business logic
into the client side in which case you would be a malicious hacker's paradise.)
All I need to know is how the server and client talk to each other. What
messages do they send back and forth, what are the content of these messages and
so on. That is the crux. As for what protocol I would use, I would design it to
be protocol agnostic. Not difficult if you implement interfaces and proper
Object oriented design. Then I would make a default implementation probably
using straight TCP and sockets and let someone that knows WebDAV (AT ALL) work
on that. Or I could implement the HTTP interface.
Now I suppose I could drop a listener on an HTTP socket and try to figure out
the scheme but that would be a painful way to do it. It would be much better to
hit the ground running with the design docs.
"Garrett Rooney" <firstname.lastname@example.org> wrote in message
> Robert Simmons wrote:
> > So the question is how could I get started? What directories do I need for
> > client side work? Which should I read first, second so on. Are there any
> > docs talking about subversion's "language" between the client and server?
> Well, it's going to be more complex than you'd like...
> Subversion has multiple 'repository access layers' that the client
> libraries use to talk to the repository. One uses direct calls into
> Berkeley DB to connect directly to the repository on local disk, one
> uses a WebDAV dialect, and one uses a custom TCP protocol. If you
> wanted to do this you'd probably pick one (either DAV or the custom TCP
> protocol probably, since you'd want to talk to a repos over the
> network), and you'd have to implement both that, the client libraries,
> and the working copy libraries (and man, those are nontrivial). In
> general, it's a HUGE amount of work, and I personally don't recommend
> it. Using the SWIG or JNI bindings to call into the existing client
> libraries is /way/ more feasable.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Oct 22 00:18:36 2003