Storing and retrieving content

To store and retrieve content, Blueriq offers the IContentManager interface. This interface allows plugins to create, read, update and delete content.

Since Blueriq 17.4, Blueriq also offers an extension to this interface: the IChannelContentManager interface, which adds four methods that make use of the Java NIO API. These methods are an alternative to the stream-based equivalents in the IContentManager interface, which have been deprecated. As the deprecated methods might be removed in a future release, and as using the NIO-based API should bring performance improvements, it is advised to always implement the IChannelContentManager instead of an IContentManager from Blueriq 17.4 onwards.

At the lowest level, content managers use an IConnection to serialize and deserialize the data. An IConnection can be a connection to anything, e.g. the file system, a database or even a REST service. Projects may write their own connections and content managers to suit their specific needs or use one of the predefined content managers. 

 The following implementations are always available:

• FileContentManager, this content manager uses a IFileSystemConnection to read and write the content to a path on the file system.
• MemoryContentManager, this content manager uses the IMemoryConnection and stores the content in-memory. This content manager is strictly for development and unit test purposes.

For more information see the following sections:

• Defining a new connection
• Implementing a custom content manager
• Using a content manager