Structs§
- A binder request
- Bridge descriptor
- Encrypted binder request data. Uses a crypto-box-like construction.
- Encrypted binder response (encrypted Result)
- Exit descriptor
- An HTTP-based BinderClient implementation, driven by ureq.
- An HTTP-based BinderServer implementation. It uses
async-h1
underneath, driven by an internal executor so that it exposes a synchronous interface. - A BinderClient implementation wrapping multiple BinderClients.
- Information about a user’s subscription
- Information for a particular user
Enums§
- Error type enumerating all that could go wrong needed: e.g. user does not exist, wrong password, etc.
- Data for a binder request
- Binder response
Traits§
- Trait that all binder clients implement.
- Trait that all binder transport servers implement.
Functions§
- Encrypts it to the reply key
Type Aliases§
- Either a response or a binder error