[
https://issues.apache.org/jira/browse/CONNECTORS-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690194#comment-13690194
]
Maciej Lizewski commented on CONNECTORS-727:
--------------------------------------------
it is already done and works like this:
in getDocumentVersions you call API "items" which return metadata and
optionally contents which can be only simple text. When document is binary or
more complex - "items" API call should not return <content> tag for such
document and then connector will make separate call to API "item" passing its
id and treat all returned stream as document body (so you can return any binary
data). Call for document body ("item") is done in processDocuments of course.
the reason I introduced also optional <content> tag in metadata response is
because I wanted the API to be fine grained and allow to reduce required calls
in very simple cases.
I provided also site documentation which describes everything and also
"API.txt" file inside connectors directory.
> generic connector
> -----------------
>
> Key: CONNECTORS-727
> URL: https://issues.apache.org/jira/browse/CONNECTORS-727
> Project: ManifoldCF
> Issue Type: Improvement
> Reporter: Maciej Lizewski
> Assignee: Karl Wright
>
> OK, this is tricky, but really nice idea. I was thinking about indexing some
> sources which do not have API, or API does not provide information needed by
> Manifold, or there is dedicated system and IT team that can easily add some
> API.
> Now you have to write dedicated connector and probably some API extension,
> plugin, etc that would talk with each other to provide seeds, versions and
> documents. Which requires knowledge on how to write Manifold connectors AND
> knowledge about system - there is no so many programmers that know both
> systems :)
> So lets make things easier - provide "generic" Manifold connector that works
> with "generic" API (ie XML over HTTP which is *really* easy to implement in
> any language). This API and protocol are strictly defined and specified. Then
> to integrate with the custom document repository one has to only implement
> API entry point which follow those specifications.
--
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
