on 07/30/2011 08:30 PM Ryan Schmidt said the following:
>>>> Sorry, I did not mention that I am writing a pure PHP client
>>>> that needs to run on an environment on which the svn program is
>>>> not available, nor any SubVersion PHP extensions are available.
>>>> So using anything based on libsvn is not an option for me
>>> That's.... ridiculous. Use an svn php extension. Or if you must,
>>> call the svn command line program. Don't reinvent the wheel,
>>> because you probably won't get it quite right, and you'll cause
>>> weird error messages or possibly even repository corruption.
>> Maybe I was not clear, but I really need to access SubVersion
>> repositories in third-party environments on which there is no
>> subversion client nor any PHP SubVersion extension.
>> I can already do it to access CVS and Git repositories, there is no
>> reason I cannot do it for SubVersion.
>> I understand what you are saying not getting it quite right, but I
>> do not have an option, so I have to do it all in pure PHP.
>> I have already a pure PHP implementation working with most
>> repositories but I am getting error 400 when accessing some
>> repositories over HTTPS and I could not figure what am I doing
>> I am also skilled in C programming for many years but that is not
>> an option to run my code in environments that I do not control.
>> So, would you be able to be so kind to help locating the svn
>> command code that I need to hack to make it show the HTTP dialog?
> I'm not able to help with that because I'm not familiar with the
> Subversion source code.
OK, I understand.
> But you understand why even if I knew I would be disinterested in
> helping you. The Subversion libraries have been in development for 11
> years, work great, and do exactly what you want, but you're saying
> nope, you're going to recreate them from scratch, except it doesn't
> work all the time, so you ask for help from the group that answers
> questions about the libraries, whose members are obviously going to
> say this is an already solved non-problem: use the libraries.
Trust me, I would rather rely on the svn command precisely because what
you said, after 11 years of development it can handle all the quirks of
all the WebDAV version variants and bugs.
I am not masochist. I do not want to deal with all that if I had a choice.
> If you can install PHP, why can't you install the Subversion
> libraries and PHP extension?
I can install whatever I want in my servers, but I am developing a
SubVersion client that will run on third party shared hosting servers
which do not have the svn program installed. So I have to rely on PHP
net access support. That is why.
> The Subversion libraries are going to continue to evolve, as is the
> network protocol. For example, Subversion used to only be able to use
> neon for talking to http servers, but now can use serf which perhaps
> offers better performance, and serf becomes the default in Subversion
> 1.7; which of these methods are you emulating? So this isn't even a
> one-time task you're contemplating; this is an ongoing duplicate
> maintenance effort you're committing yourself to.
I am well aware of that, but I hope now you understand why that option
is not available to me.
BTW, is there any documentation for that serf library so I can figure
how it is used in the svn command?
Received on 2011-07-31 03:02:53 CEST