Hello dear forum members!
We developed an Adobe Drive CMIS connector for our DAM system and noticed a major navigation performance degradation
when updating CMIS connector on windows client systems from Version 4.0 to Version 4.2 or CC.
When visiting a folder:
Version 4.0 does a getChildren request ("children" url) and is finished: 1 call
Version 4.2 and CC do a getChildren request and IN ADDITION call:
- getObjectParents ("parents" url) for each object in folder
- getObjectParents for folder of path of each object
So lets say you have some folderX with path
containing 500 images of some photo session that needs sorting you get
500x getObjectParents (one for each image)
2x500x getObjectParents (2 for each folder of path of each image)
in sum: 1501 calls until that same folder gets displayed.
Any chance that this gets fixed on Adobe Drive CMIS connector?
Can we do something on server side to prevent that behavior?
Does Adobe Drive support paging in big folders?
Anything else we can do to help?
I've got the exact same problem with the CMIS Connector under Windows and posted it already in July here, still no answer from Adobe. We switched to a custom connector using the SDK in the meanwhile to have more control over what requests are sent.
I want to acknowledge that we are aware that this issue has been reported.
There were indeed changes to the CMIS connector in the Adobe Drive 4.2 release that was released earlier this year; one of which was to enable Adobe Drive (when using the CMIS Connector) to show more than 25 files/folders: http://helpx.adobe.com/drive/release-note/drive-42-release-notes.html
When we have more information to share…an update will be provided.
Plus one on this issue, and a nudge for an update. Is a custom connector in the SDK the only way around this? I tried using a caching proxy but it breaks other interactions -- possibly more clever cache rules would work?