Architecture

Distinction from the jadice web toolkit

The jadice web toolkit provides integrators with an SDK to create their own viewer application
or integrate it into an existing application. It offers full access to the interfaces of
the jadice web toolkit and the jadice document platform.

The jadice web viewer, on the other hand, is a ready-to-use application that can either run
as a standalone solution or be lightweightly integrated into an existing application.
Customization options are primarily limited to styling and configuration aspects.

Loading and Displaying Documents

A loading process typically starts with a request from the client’s browser interface.

• The client transmits a document to be displayed to the server.
• The server temporarily stores the document and sends information about it,
  such as page numbers and sizes, back to the client.
• The client sequentially requests individual pages from the server. These pages
  are rendered by the server as PNG or WebP images (so-called tiles).
• The client can also provide URIs to the server, allowing the server to
  download documents from the specified URIs.

Communication requires a backend implementation as a Spring Boot application.

The client itself runs entirely in JavaScript within the browser.