
RIDC – Proprietary Thin-Client API for Communicating with Content Server
Advantages: • Easy to learn for those with extensive Content Server experience (very little abstraction from Content Server)
• With proper development, can be highly scalable, but requires more attention to detail
• Very lighweight; uses less system resources than CIS for enterprise applications
• Supports connecting via web server (authentication required for every request) or directly to Content Server socket (trusted connection).
Disadvantages:
• No configurable caching; all caching must be coded into application
• No built-in application logging; all logging must be coded into application
• Requires extensive Content Server architecture knowledge
• Only available for Java application.

Laisser un commentaire