[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659540#comment-13659540
]
Tommaso Teofili commented on JCR-3534:
--------------------------------------
>that doesn't make it secure... the problem is that that value should not be
>stored as plain text value in a file that is
readable for everyone that can write "new File....".
> Putting it in the datastore as outlined above would not necessarily make
> access more difficult
I agree with Jukka on this point, if one has access to repository.xml then
he/she is already "root" on the whole repository
The problem with storing the reference key in the datastore is that such a
thing cannot be done via the DataStore API as that doesn't offer a method to
add a DataRecord given a DataIdentifier (which would have to be fixed to let
the AbstractDataStore know which identifier is assigned to the reference key
record), therefore each DS implementation should do it in its own specific way.
Given that it seems to me the best option is having a getter and setter in the
AbstractDataStore for the referenceKey (better name than secret), then
subclasses can extend the getter and define a DS implementation specific way of
storing/retrieving the referenceKey if that's not provided in the configuration.
> Efficient copying of binaries across repositories with the same data store
> --------------------------------------------------------------------------
>
> Key: JCR-3534
> URL: https://issues.apache.org/jira/browse/JCR-3534
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-api, jackrabbit-core
> Affects Versions: 2.6
> Reporter: Felix Meschberger
> Assignee: Tommaso Teofili
> Attachments: JCR-3534.2.patch, JCR-3534.3.patch, JCR-3534.4.patch,
> JCR-3534.patch, JCR-3534.patch
>
>
> we have a couple of use cases, where we would like to leverage the global
> data store to prevent sending around and copying around large binary data
> unnecessarily: We have two separate Jackrabbit instances configured to use
> the same DataStore (for the sake of this discussion assume we have the
> problems of concurrent access and garbage collection under control). When
> sending content from one instance to the other instance we don't want to send
> potentially large binary data (e.g. video files) if not needed.
> The idea is for the sender to just send the content identity from
> JackrabbitValue.getContentIdentity(). The receiver would then check whether
> the such content already exists and would reuse if so:
> String ci = contentIdentity_from_sender;
> try {
> Value v = session.getValueByContentIdentity(ci);
> Property p = targetNode.setProperty(propName, v);
> } catch (ItemNotFoundException ie) {
> // unknown or invalid content Identity
> } catch (RepositoryException re) {
> // some other exception
> }
> Thus the proposed JackrabbitSession.getValueByContentIdentity(String) method
> would allow for round tripping the JackrabbitValue.getContentIdentity()
> preventing superfluous binary data copying and moving.
> See also the dev@ thread
> http://jackrabbit.markmail.org/thread/gedk5jsrp6offkhi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
