eric wrote:
>
> Yes, however it might make writing some types of clients, particularly
> repository browsers a lot easier.
Compared to using Subversion's public API? I seriously doubt that.
> Branko Čibej wrote:
>
>> John Peacock wrote:
>>
>>> I think there is little chance that writing a SOAP interface to
>>> Subversion (whatever that means since SOAP is a transport layer not
>>> an application layer) would have any bearing on using Subversion on
>>> a non-Apache web server.
>>
>>
>>
>> Indeed. You'd still have to write a mapping between the soap-wrapped
>> RPC and the SVN repository layer, which amounts to writing a plug-in
>> for your particular SOAP server. The interfaces are marginally more
>> portable than Apache's module API, but it would still be a
>> significant amount of work for every supported server.
>>
>> Besides, I don't see any benefit in it; a) you can always run Apache
>> alongside another server, b) you lose performance by having to wrap
>> everything with SOAP envelopes, and c) there's always svnserve if
>> Apache isn't appropriate.
>>
>> -- Brane
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: dev-help@subversion.tigris.org
>>
>
--
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 7 03:06:54 2005