Community
Participate
Working Groups
Currently, we store a Long as a session property of each meta-data file which allows us to determine who last modified a particular meta-file. We should investigate whether we need to persist the Long indefinitely or whether it is enough to use the session property until the next delta. Here is one proposed alternative: - If the CVS plugin changes a meta-file, add the timestamp session property - In a delta, if the timestamp is there and matches the modification time, we're OK. If the timestamp is wrong or not there, the meta-file was modified by a third party. - In either case, clear the session property after it is used in the delta
We need to investigate time cost of making/clearing session properties. For resources which you are doing a lot of CVS operations against, this could be expensive. However, good savings for cases such as replacing from latest/update then not doing anything with that project.
Adding my name to the cc list as we are now tracking performance issues more closely. Please remove the performance keyword if this is not a performance bug.
This was added at some point in 3.0
