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

RE: How to differentiate the PROPFIND /svn/repo/!svn/vcc/default for commit Vs some read operation

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: Tue, 22 Dec 2009 23:27:38 +0530

>>
>> May be I can set some persistent data structure at the connection scope
>> remembering the invocation of prior 'MKACTIVITY' and
>> decide whether it is PROPFIND for commit or 'some read ops'.
>>
>> Any thoughts!

>Perhaps have the client set a header or do something different in this
>case? But, doing connection-scope variable is a very very bad bad bad
>bad idea. You can not assume that the connection is persistent. --

Implementing the client headers like this needs everyone to upgrade their clients.
If we do that successfully we can also *partially* improve the operational logging precision(of course the header can be spoofed!).

With regards
Kamesh Jayachandran
Received on 2009-12-22 18:58:16 CET

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

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