RE: How to differentiate the PROPFIND /svn/repo/!svn/vcc/default for commit Vs some read operation
>> 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!).
Received on 2009-12-22 18:58:16 CET
This is an archived mail posted to the Subversion Dev