[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-168) URL to id mapping
[ http://tools.oasis-open.org/issues/browse/CMIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11536#action_11536 ] Florian Mueller commented on CMIS-168: -------------------------------------- b) seems to be the worst solution. If I'm looking at it from a lazy client developer perspective I already have code that deals with collections. The types and changes collections are also collections that don't accept POST. The main difference would be that this new collection would return a feed with only one entry. I understand that the template mechanism is the cleaner approach, though. If we would introduce it here would it make sense to replace the GET-only collections as well with templates? I can imagine passing a type id the same way. Additionally, if we add folderbypath here we would need an equivalent in the SOAP binding. > URL to id mapping > ----------------- > > Key: CMIS-168 > URL: http://tools.oasis-open.org/issues/browse/CMIS-168 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Components: REST/AtomPub Binding > Affects Versions: Draft 0.61 > Reporter: David Nuescheler > Assignee: Al Brown > > reported in various discussions during the PlugFest in Basel, my interpretation may be off. > Currently there is no way to map document and folder ids to urls on the client side. > This will either lead to a large number of additional roundtrips or to very stateful clients > that rely on the stability of that mapping (which i am not sure if this would be legal). > So it would be great if there was a simple mapping from id's to URLs for both folders and > documents. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]