[
https://issues.apache.org/jira/browse/STANBOL-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler updated STANBOL-573:
----------------------------------------
Fix Version/s: 0.10.0-incubating
> Add Factory for ContentItems and Blobs
> --------------------------------------
>
> Key: STANBOL-573
> URL: https://issues.apache.org/jira/browse/STANBOL-573
> Project: Stanbol
> Issue Type: New Feature
> Components: Enhancer
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Fix For: 0.10.0-incubating
>
>
> Currently the used implementation for ContentItems/Blobs is hardcoded for the
> Stanbol Enhancer. The same is true for other components that do use the Java
> API of the Enhancer (e.g. the Contenthub).
> The introduction of a ContentItemFactory that registers itself as OSGI
> service would allow to change the used implementation based on a
> configuration.
> A simple usage scenario where this would make sense in the enhancement of big
> media files. Currently those files are kept in-memory, because thats the way
> how the currently used InMemoryContentItem/InMemoryBlob implementation works.
> While having the data in memory is best suited for typically enhancement
> requests (small to medium sized textual content) this might become
> troublesome for users that whant to extract and enhance metadata from media
> files (e.g. ID3 tags from MP3 or Exif metadata from TIF images). The facrory
> pattern would allow to configure a ContentItem/Blob implementation that keeps
> the parsed content in temporary files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
