You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2005/07/27 16:14:44 UTC

[jira] Resolved: (JCR-174) Contrib JCR-Server: improve handing of strong etags

     [ http://issues.apache.org/jira/browse/JCR-174?page=all ]
     
angela resolved JCR-174:
------------------------

    Resolution: Fixed

> Contrib JCR-Server: improve handing of strong etags
> ---------------------------------------------------
>
>          Key: JCR-174
>          URL: http://issues.apache.org/jira/browse/JCR-174
>      Project: Jackrabbit
>         Type: Improvement
>     Reporter: angela
>     Assignee: angela
>     Priority: Minor

>
> copied from dev-mail:
> [..]
> so... could we
> - delegate the calculation of the etag to the
>   commands, letting them decide on whether they are able
>   to provide any and whether it would be a strong or a
>   weak one?
> - remove that additional method in NodeResource that is
>   not used? 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Resolved: (JCR-174) Contrib JCR-Server: improve handing of strong etags

Posted by Angela Schreiber <an...@day.com>.
hi brian

> i didn't even think to open jira issues for the various things we've 
> discussed on the list, but that seems like a good idea, so i'll start 
> diong that.

yes... i think that would be fine.

- keeping track of changes
- having a issue number for the commits
- easier to find discussions related to a particular
   modifications
- possibility to track if a discussion resulted in
   commits (or was resolved 'wontdothat' ;).
- reminder for me ;)

> if it's not a pain, that would be great for these particular changes. in 
> general, i don't think it's necessary.

done.
i attached a diff to JCR-174. but it contains all the
modifications not only those related to the etag issue.
the latter affects

contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\PrimaryItemExportCommand.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\AbstractExportCommand.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\DirListingExportCommand.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\FileExportCommand.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\server\io\ExportContext.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\webdav\simple\DavResourceImpl.java
contrib\jcr-server\server\src\java\org\apache\jackrabbit\webdav\simple\NodeResource.java
contrib\jcr-server\webdav\src\java\org\apache\jackrabbit\webdav\WebdavRequestImpl.java 


regards
angela


Re: [jira] Resolved: (JCR-174) Contrib JCR-Server: improve handing of strong etags

Posted by Brian Moseley <bc...@osafoundation.org>.
Angela Schreiber wrote:

> since initially there was no jira issue, i didn't
> expect those changes to be urgent... better
> let me know the next time...

i wouldn't call them urgent - i'm just impatient :)

i didn't even think to open jira issues for the various things we've 
discussed on the list, but that seems like a good idea, so i'll start 
diong that.

> if you are waiting for it, i can attach a patch
> to the jira issue... since we handle things a
> little different, i normally avoid that extra
> effort.

if it's not a pain, that would be great for these particular changes. in 
general, i don't think it's necessary.

Re: [jira] Resolved: (JCR-174) Contrib JCR-Server: improve handing of strong etags

Posted by Angela Schreiber <an...@day.com>.
hi brian

i marked them fixed, because i'm done. i use
to make my issue 'closed' if the modifications
are present in subversion (pls let me know if
that's not the proper workflow). however,
i cannot force any changes to be commited.

since initially there was no jira issue, i didn't
expect those changes to be urgent... better
let me know the next time...

if you are waiting for it, i can attach a patch
to the jira issue... since we handle things a
little different, i normally avoid that extra
effort.

regards
angela


Brian Moseley wrote:
> angela (JIRA) wrote:
> 
>>      [ http://issues.apache.org/jira/browse/JCR-174?page=all ]
>>      angela resolved JCR-174:
>> ------------------------
>>
>>     Resolution: Fixed
> 
> 
> both this and JCR-175 are marked fixed, but i haven't seen any commit 
> messages regarding the changes. are they sitting in somebody's mailbox 
> waiting to be committed?
> 
> if so, please register my vote to get them in sooner rather than later 
> :) i could really use them this week, for a demo before heading off to 
> OSCon next week.
> 
> if not, i'm on crack and will take appropriate measures.
> 
> thanks!


Re: [jira] Resolved: (JCR-174) Contrib JCR-Server: improve handing of strong etags

Posted by Brian Moseley <bc...@osafoundation.org>.
angela (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/JCR-174?page=all ]
>      
> angela resolved JCR-174:
> ------------------------
> 
>     Resolution: Fixed

both this and JCR-175 are marked fixed, but i haven't seen any commit 
messages regarding the changes. are they sitting in somebody's mailbox 
waiting to be committed?

if so, please register my vote to get them in sooner rather than later 
:) i could really use them this week, for a demo before heading off to 
OSCon next week.

if not, i'm on crack and will take appropriate measures.

thanks!