Expand description
Definition of the protocol needed to communicate with the daemon
Structs§
- AnyFs
Ref - A reference to a filesystem in the SynchroList handled by the brume daemon.
- AnySynchro
Creation Info - The information needed to create a new synchro between filesystems
- AnySynchro
Ref - A
Synchrowhere theBackendfilesystems are only known at runtime. - Brume
Service Client - The client stub that makes RPC calls to the server. All request methods return Futures.
- Local
DirCreation Info - Nextcloud
FsCreation Info - Info needed to create a new connection to a nextcloud server
- Serve
Brume Service - A serving function to use with ::tarpc::server::InFlightRequest::execute.
- Synchro
Id - An id that uniquely identify a pair of synchronized FS
- Virtual
Path - A wrapper type that allows doing path operations on strings, without considerations for any concrete file system. These paths are supposed to be absolute and should start with a ‘/’.
- Virtual
Path Buf - Similar to the distinction with Path and PathBuf, this is a VirtualPath that owns the underlying data.
Enums§
- AnyFs
Creation Info - The information needed to create a FS that can be synchronized.
- AnyFs
Description - The information needed to describe a FS that can be synchronized.
- Brume
Service Request - The request sent over the wire from the client to the server.
- Brume
Service Response - The response sent over the wire from the server to the client.
- Synchro
Side - Synchro
State - User controlled state of the synchro
- Synchro
Status - Computed status of the synchro, based on synchronization events
Constants§
- BRUME_
SOCK_ NAME - Name of the socket where the clients should connect
Traits§
- Brume
Service - Brume
Service Stub - The stub trait for service
BrumeService.