You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Julian Foad (JIRA)" <ji...@apache.org> on 2018/10/19 09:27:00 UTC

[jira] [Updated] (SVN-4045) Earlier detection of failed locking preconditions during commits

     [ https://issues.apache.org/jira/browse/SVN-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Foad updated SVN-4045:
-----------------------------
    Component/s:     (was: src)

> Earlier detection of failed locking preconditions during commits
> ----------------------------------------------------------------
>
>                 Key: SVN-4045
>                 URL: https://issues.apache.org/jira/browse/SVN-4045
>             Project: Subversion
>          Issue Type: Improvement
>    Affects Versions: 1.7.x
>            Reporter: C. Michael Pilato
>            Priority: Major
>              Labels: ev2
>             Fix For: 1.10-consider
>
>
> {noformat:nopanel=true}
> A CollabNet customer has requested earlier detection at commit time of the sorts
> of lock-related precondition failures that will cause the whole commit to fail.
>  Specifically, it would be nice if a commit doomed to fail because it attempts
> to modify a locked resource without ownership of that lock would fail before the
> costlier part of the commit process -- transmitting the modified content -- began.
> The required program flow (announcing to the server the paths which are
> scheduled for modification, providing any held tokens for those paths, and then
> continuing to the actual modification phase) might be a better fit for Ev2
> (Editor, v2 -- svn_editor.h).
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)