As a developer integrating Pillarbox's standard connector I would like to be able to add download support quickly, without too much work required to manage persistence.
Hints
We currently let data sources return arbitrary metadata M. We could restrict this metadata to PlayerData<CustomData> basically combining a non-generic PlayerMetadata and CustomData. Whether this could make our API simpler to use and standard implementations easier to implement remain to be investigated (since the original metadata is degraded in the process).
Acceptance criteria
- A simple storage is provided for the standard connector, with which adding download support is easy.
- Custom data and custom/encrypted asset support should be possible with limited work.
Tasks
As a developer integrating Pillarbox's standard connector I would like to be able to add download support quickly, without too much work required to manage persistence.
Hints
We currently let data sources return arbitrary metadata M. We could restrict this metadata to
PlayerData<CustomData>basically combining a non-genericPlayerMetadataandCustomData. Whether this could make our API simpler to use and standard implementations easier to implement remain to be investigated (since the original metadata is degraded in the process).Acceptance criteria
Tasks