[ 
https://issues.apache.org/jira/browse/JCR-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662388#action_12662388
 ] 

Jukka Zitting commented on JCR-1892:
------------------------------------

> Sure, what about "The string is normally about 50 characters long."

Or: "The returned string contains only ASCII letters and digits and is at most 
128 characters long." Both limitations are generic enough for most identifier 
formats (even a hex representation of a huge 512-bit hash), and they allow 
client applications to easily (no quoting) and efficiently (bounded size) use 
the returned strings.

> What about getRecordIfStored()?

I think the current getRecord() is fine. If you already have a DataIdentifier 
for something, then it's highly likely that the corresponding record also 
exists in the DataStore, and an exception would truly be exceptional.


> Unique ID for org.apache.jackrabbit.value.BinaryValue
> -----------------------------------------------------
>
>                 Key: JCR-1892
>                 URL: https://issues.apache.org/jira/browse/JCR-1892
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: jackrabbit-jcr-commons
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>         Attachments: JackrabbitValue-api.patch, JackrabbitValue-core.patch
>
>
> BinaryValue should have a method get the unique identifier (if one is 
> available). That way an application may not have to read the stream if that 
> value is already processed.
> When the DataStore is used, a unique identifier is available, so probably 
> this feature is quite simple to implement.
> See also http://www.nabble.com/Workspace.copy()-Question-...-td20435164.html 
> (but please don't reply to this thread from now on - instead add comments to 
> this issue).
> Another feature is getFileName() to get the file name if it is stored in the 
> file system. This method may need a security mechanism, for example 
> getFileName(Session s) so that the system can check it. In any case the file 
> should not be modified, but maybe knowing the file name is already too 
> dangerous in some cases.

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

Reply via email to