OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (CMIS-786) Symbolic Link Extension Proposal


    [ https://issues.oasis-open.org/browse/CMIS-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62199#comment-62199 ] 

Florian Mueller commented on CMIS-786:
--------------------------------------

I have few questions.

* Let's say a symbolic link is filed in a folder. The referenced object doesn't exist or the user has no permissions to see the references object. When a client calls getChildren on the folder, what is returned? The symbolic link object or nothing? Both are problematic.
* If the symbolic link object and the referenced object are in the same folder and the client calls getChildren, does the repository return the object twice in the response? (If so, that might break some clients. If not, it is inconsistent.)
* How can a client identify if an object ID belongs to a symbolic link or to another object? That's necessary to decide of an updateProperties call with the disableDereferencing makes sense.
* What should happen if getDescendants or getFolderTree run into a cycle? If this throws an exception, then a single user can easily break a lot (intentionally or unintentionally).

> Symbolic Link Extension Proposal
> --------------------------------
>
>                 Key: CMIS-786
>                 URL: https://issues.oasis-open.org/browse/CMIS-786
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Ken Baclawski
>            Priority: Minor
>
> This extension provides for a subclass of cmis:item called cmis:symbolicLink.  An object of type cmis:symbolicLink has an attribute referenceId that specifies an object Id or latest accessible state identifier.  When the Id of a  symbolic link item is specified in a service request, the referenceId attribute of the item may be used instead of the specified symbolic link Id.  The replacement of the symbolic link Id with another Id is called dereferencing.  When dereferencing is performed, it is recursive: if the referenceId of a symbolic link item is itself the Id of a symbolic link item, then that symbolic link Id is also dereferenced.  If a dereferencing cycle is detected, a cmis:dereferenceException is thrown.  Dereferencing of symbolic links in a service call can be explicitly enabled or disabled by an optional dereferenceSymbolicLinks parameter.  If the dereferenceSymbolicLinks parameter is not specified as FALSE in a service call, then symbolic link dereferencing is performed, i.e., the default value of the dereferenceSymbolicLinks parameter is TRUE.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]