The bookshelf and the CloudReader’s deployed location are typically the same, but do not need to be so. The CloudReader is downloaded each time the user creates a new instance of the CloudReader. Another distinction is while RCS loads the user’s books into a private filesystem managed by Chrome on the user’s computer, the CloudReader loads its books from a “bookshelf” located somewhere on the web. The CloudReader, on the other hand, runs in almost all browsers. The key difference is that RCE is tightly wedded to Google Chrome and therefor works only where Chrome is available.

The CloudReader is very similar to the Chrome Application – and they share almost all their code. It imports the user’s books into a private file-system on the user’s computer. It only works with Google Chrome since it leverages the built-in capabilities provided by the Chrome framework. It is under constant development to provide more features and capabilities. Unlike the Readium SDK Launchers, RCA is a relatively polished, full-featured application. It supports virtually all of the EPUB 3.0.1 specification. It is a full-fledged, functional EPUB reading system. This sub-project consists of an Application to Google Chrome. The diagram below illustrates the major aspects of their architectures. The Chrome Application and the CloudReader share approximately 95% of their code, the primary difference is where their EPUB “library” is located and how they fetch EPUB resources. readium-js-viewer: This is the application layer which manages the user-interface.readium-shared-js: This is exactly the same code as used in the SDK implementation (hence the ‘shared’ name),.readium-js, which is the core (equivalent to the C++ Core in the SDK) and provides basic services, manages the EPUB package, metadata, navigating and fetching resources and so on,.Readium JS comprises two sub-projects, Readium Chrome Application and the Readium CloudReader.

Readium google chrome