Rip-Server

The Rip-Server is designed to accept and process OTP jobs integrating several input mechanisms and job processors.
The feature is under development and will be available in the next OTP release.

Rip-Server Input Mechanism

Input mechanism is used to accept jobs from various devices or systems, using device/system specific rules. Rip-Server contains build-in mechanism for serving common tasks. Any special devices are supported by the plug-ins (extensions). Build-in input mechanisms for the Rip-Server are:

     - Folder Watcher - it monitors folders for dropped items (files or nested folders);

     - URL Acceptor - it picks up the http request performed to pass the URL pointing to the job folder of file;

     - SOAP acceptor - it can invoke the processing function by the external application or system via the SOAP protocol, passing to it the URL to job folder or file that needs to be processed.

Rip-Server Processing Mechanism

The Rip-Server processes jobs by build-in processors and extensions that perform common tasks. For instance, the processors are:

     - Content uploader - transfers any matched files from input job to the OTP server. Content uploader uses configured list of mime types that are accepted as is and copied to the OTP server.

     - Thumbnail generator - generates thumbnails for all possible file formats. All files are passed through this processor before they are delivered to the OTP server.

Other processors may be attached through the plugin mechanism. Any existing Lucid Dream's applications, such as TIFFPager, OTPproof and others can be attached using this mechanism.

Rip-Server security

In order to protect the Rip-Server from unauthorized connections, it uses user-based access mechanism. The Rip-Server may contain an arbitrary list of users who are allowed to connect to the server. A user should have one of the defined permissions to access the Rip-Server.

In addition, the Rip-Server contains the access table, where IP addresses of allowed/denied hosts are set. This table realizes the commonly used scheme: "deny any addresses but ..." or "allow from any addresses but ...".
The Rip-Server administrator may use this table to block entire networks or particular hosts. The Rip-Server would not allow a valid username/password to connect if the originating address was entered into the access list table and marked there as blocked out.