You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2009/12/08 11:35:18 UTC

[jira] Commented: (COMDEV-6) permit do_io_write after open_read to enable atomic overwrite of an existing object

    [ https://issues.apache.org/jira/browse/COMDEV-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787398#action_12787398 ] 

Ross Gardler commented on COMDEV-6:
-----------------------------------

This is not intended for the ComDev isue tracker. If you let us know which project it belongs to we'd be happy to move it for you.

> permit do_io_write after open_read to enable atomic overwrite of an existing object
> -----------------------------------------------------------------------------------
>
>                 Key: COMDEV-6
>                 URL: https://issues.apache.org/jira/browse/COMDEV-6
>             Project:  	 Community Development 
>          Issue Type: New Feature
>            Reporter: John Plevyak
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> A number of more stateful protcols would benefit from the ability to atomically replace an existing object.
> By adding the ability for non-HTTP protocols to retrieve a block of untyped header information from the
> CacheVConnection and the ability to convert a read into a write (with an error if it is overwritten by someone
> else) we can handle such protocols.
> Both of these ability are already present in the HTTP cache codepaths so generalizing and exporting them
> seems logical.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.