Rasterex APINPM Package/docs/current-architecture

Current Rasterex Architecture

A current-only map of the Viewspace product stack, integration boundaries, data ownership, and backend responsibilities.

Use This Page First

Use this page to establish the current product vocabulary before choosing an integration or interpreting an API reference. It prevents historical product names and legacy implementation patterns from being treated as current.

Current Product Stack

Viewspace is the current Rasterex product. Canvas is the embedded viewing and annotation surface within Viewspace. The current npm SDK package is @rasterex/viewer.

  • Use Viewspace for the current product-level term.
  • Use Canvas only for the embedded viewing and annotation surface.
  • Use @rasterex/viewer exactly for the current npm SDK package.
  • ODA supports CAD rendering and backend operations.
text
Viewspace
  ↓
Canvas
  ↓
@rasterex/viewer
  ↓
Backend Engine / Rasterex Backend
  ↓
ODA (Open Design Alliance)
Current Product Stack

Data and Processing Boundaries

Customers host and own their database. Rasterex has no access to that database.

Annotation handling, DWG structure parsing, and IFC structure parsing are backend operations.

  • Do not describe a customer database as Rasterex-hosted or Rasterex-accessible.
  • Do not present backend processing responsibilities as browser-side SDK behavior.

Integration Boundaries

NPM SDK Quick Start

Set up the current `@rasterex/viewer` package in a package-based application.

PostMessage Quick Start

Embed the Canvas viewing surface in an iframe and communicate through browser messages.

Package-based applications use the NPM SDK. Applications embedding the Canvas viewing surface in an iframe use browser messages. These integration modes have separate APIs and event contracts.

Use the documentation page for the selected integration mode. Do not infer an NPM SDK method from a browser-message command, or the reverse.

  • Choose the NPM SDK for package-based applications such as React, Next.js, Vue, Angular, Vite, and TypeScript applications.
  • Choose PostMessage only when the host embeds Canvas in an iframe and communicates through browser messages.
  • For an existing NPM project, preserve its installed @rasterex/viewer version and verify API shape against its declarations.

Safe Current Terminology

Keep the current product hierarchy intact in documentation, code comments, diagrams, and AI guidance. The order matters: Viewspace is the product; Canvas is its embedded surface; @rasterex/viewer is the npm SDK package.

Legacy Boundary

RxView360 and the standalone Angular viewer application are not part of the current architecture.

If legacy documentation appears to conflict with current documentation, the current documentation always takes precedence.