Struct GRPCDirectoryServiceWrapper 

pub struct GRPCDirectoryServiceWrapper<T> {
    directory_service: T,
}

Fields

directory_service: T

Implementations

impl<T> GRPCDirectoryServiceWrapper<T>

pub fn new(directory_service: T) -> Self

Trait Implementations

impl<T> DirectoryService for GRPCDirectoryServiceWrapper<T>

where T: DirectoryService + Clone + Send + Sync + 'static,

type GetStream = Pin<Box<dyn Stream<Item = Result<Directory, Status>> + Send>>

Server streaming response type for the Get method.

fn get<'life0, 'async_trait>( &'life0 self, request: Request<GetDirectoryRequest>, ) -> Pin<Box<dyn Future<Output = Result<Response<Self::GetStream>, Status>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

Get retrieves a stream of Directory messages, by using the lookup parameters in GetDirectoryRequest. Keep in mind multiple DirectoryNodes in different parts of the graph might have the same digest if they have the same underlying contents, so sending subsequent ones can be omitted.

fn put<'life0, 'async_trait>( &'life0 self, request: Request<Streaming<Directory>>, ) -> Pin<Box<dyn Future<Output = Result<Response<PutDirectoryResponse>, Status>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

Put uploads a graph of Directory messages. Individual Directory messages need to be send in an order walking up from the leaves to the root - a Directory message can only refer to Directory messages previously sent in the same stream. Keep in mind multiple DirectoryNodes in different parts of the graph might have the same digest if they have the same underlying contents, so sending subsequent ones can be omitted. We might add a separate method, allowing to send partial graphs at a later time, if requiring to send the full graph turns out to be a problem.