How readium/readium-lcp-server works
Readium LCP Server protects EPUB publications, serves LCP licenses, and manages license-status operations; it also includes a non-production micro-CMS demo. The main workflow is publication encryption and storage, followed by license generation and status lifecycle management. The graph preserves documented renewal, return, cancellation, revocation, and frontend capabilities. Edges use sampled source evidence where available; README-described relationships without a sampled caller are dashed and unverified.
Main entry points: license.go License API · pipeline.go EPUB packager · license_status.go Status operations · server.go License HTTP server
Components 20
Publication encryption
- Encrypt CLI
lcpencrypt/lcpencrypt.go - Encryption workflow
encrypt/process_encrypt.go - EPUB packager
pack/pipeline.go
LCP license service
- License HTTP server
lcpserver/server/server.go - License API
lcpserver/api/license.go - License model
license/license.go - License store
license/store.go
License status service
- Status HTTP server
lsdserver/server/server.go - Status operations
lsdserver/api/license_status.go - License status store
license_statuses/license_statuses.go - Status transactions
transactions/transactions.go
Demo micro-CMS
- Demo frontend server
frontend/server/server.go - Demo REST API
frontend/api/repository.go - Demo CMS handlers
frontend/webpurchase/webpurchase.go - Admin interface
frontend/manage/app/app.module.ts
Shared data services
- Encrypted content store
storage/interface.go - Content index
index/index.go
Other components
- Publisher CMS
- License gateway
- Reading application
Connections 19
- Publisher CMS → Encrypt CLI: submits publication
- Encrypt CLI → Encryption workflow: runs encryption
lcpencrypt/lcpencrypt.go - Encryption workflow → EPUB packager: uses packaging
encrypt/process_encrypt.go - EPUB packager → Encrypted content store: writes encrypted file
pack/pipeline.go - EPUB packager → Content index: records content
pack/pipeline.go - License HTTP server → License API: routes requests
lcpserver/server/server.go - License API → Content index: reads content
lcpserver/api/license.go - License API → License model: builds license
lcpserver/api/license.go - License API → License store: reads license
- License gateway → License HTTP server: requests license
- Reading application → License gateway: requests fresh license
- Status HTTP server → Status operations: routes requests
lsdserver/server/server.go - Status operations → License status store: updates status
lsdserver/api/license_status.go - Status operations → Status transactions: records events
lsdserver/api/license_status.go - Demo frontend server → Demo REST API: registers routes
frontend/server/server.go - Demo REST API → Demo CMS handlers: uses repository handler
frontend/api/repository.go - Admin interface → Demo frontend server: uses demo API
- Publisher CMS → License HTTP server: requests license operations
- Publisher CMS → Status HTTP server: requests status changes