Repository navigation
Replies: 1 comment
|
Thanks @FizzWhirl, this is a great write-up, and it matches where we want the plugin system to go. We're taking it on for v0.3.8 with one principle: Ether itself won't build audiobooks, comics, music or book features. v0.3.8 builds the generic infrastructure so that any content type can be added purely as a plugin, with no core changes:
We're writing the detailed design against the codebase now and will post it here for feedback before the build lands. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Goal: Extend Ether to support multiple content types (beyond its current catalogue) via its plugin system, using on-demand resolution and protocol emulation. The architecture should accommodate any content type—flat or hierarchical, single-item or container-based—without core modifications.
Core Requirements:
Content-Type–Aware Plugin Architecture
MediaKind.MediaKindmay define its own metadata schema, depending on its needs (e.g., flat vs. hierarchical, item-level vs. container-level).Catalog Provider Plugins
Resolver Plugins (On-Demand)
{pageNumber},{byteRange}, or{itemIndex}) and MIME type.Protocol Frontend Adapters
Streaming Engine Extension
Plugin SDK & Isolation
CatalogProvider,Resolver, and optionalFrontendAdapter.Matching & Scoring Logic
Caching & Eviction
Library Segregation & Permissions
Setup Validation
Deliverable: A plugin framework where each content type is a bundle of (catalog provider + resolver + optional frontend adapter), all sharing Ether's streaming core and protocol frontends. Requirements like hierarchical metadata, item extraction, fine-grained seeking, and dedicated protocol adapters are expressed generically so that any content type—present or future—can declare and fulfill them without core changes. No core modifications needed beyond the initial plugin system already released.
All reactions