Integration Guide
Design a bounded and verifiable Auto Drive integration using public libraries.
Use this sequence when adapting the public Auto Drive adapter to an application.
1
2
3
4
5
Operational requirements
Make writes idempotent where the provider contract supports it.
Do not automatically retry an ambiguous upload or transaction submission.
Limit recovery lookups by identity, caller, rate, and time window.
Escape or encode untrusted values before displaying them.
Record non-secret evidence sufficient to investigate an interrupted operation.
The public storage and XL1 packages currently follow different protocol peer lines. Keep the storage-only workflow separate until a supported combination is published and verified.
Last updated