[
https://issues.apache.org/jira/browse/JCR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641019#comment-13641019
]
Felix Meschberger commented on JCR-3534:
----------------------------------------
> To simplify development/support, the message should readable, for example
> JSON or an URL. Example (shortened)
This sounds like the old mantra in the XML-days: Everything had to be XML, bla,
bla, bla. Please just keep this simple and don't overexagerate. Having a string
of colon separated values (if the value is structured in some way) is more that
enough. Otherwise you incurr the price of parsing JSON ... Not worth it IMHO.
> Having expiry and encrypting the identifier would prevent further damage in
> case the BinaryReferenceMessage leaks.
What is the problem with this message leaking as opposed to the actual data
leaking which would be transported over the same channel completely unencrypted
? Again, this sounds like over-engineering to me.
We should leave data protection to the transport layer (e.g. SSL) and just care
to make sure that a data reference cannot be made up by an attacker (in the
sense of "try to find out whether a document exists").
> Add JackrabbitSession.getValueByContentId method
> ------------------------------------------------
>
> 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
> Attachments: 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
