Page MenuHomePhabricator

[services] Backup - Implementation structure
ClosedPublic

Authored by karol on Feb 10 2022, 6:27 AM.
Tags
None
Referenced Files
F3377830: D3158.id9655.diff
Wed, Nov 27, 7:42 AM
Unknown Object (File)
Wed, Nov 13, 12:30 PM
Unknown Object (File)
Fri, Nov 8, 10:38 PM
Unknown Object (File)
Tue, Nov 5, 6:51 PM
Unknown Object (File)
Oct 14 2024, 3:27 AM
Unknown Object (File)
Oct 13 2024, 6:27 PM
Unknown Object (File)
Oct 13 2024, 6:27 PM
Unknown Object (File)
Oct 13 2024, 6:27 PM

Details

Summary

Implementation structure based on the .proto file

Depends on D3087

Test Plan

Backup service builds successfully

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

karol edited the test plan for this revision. (Show Details)
karol added reviewers: tomek, max, varun.
This revision is now accepted and ready to land.Feb 11 2022, 1:57 AM
This revision now requires review to proceed.Feb 11 2022, 1:57 AM
This revision is now accepted and ready to land.Feb 13 2022, 7:58 PM

Is grpc::ServerReaderWriter a blocking or non-blocking way to handle a bidi stream? (Or does it work either way?)

For now, I'm using a sync API here. Once it's fully figured in the tunnelbroker so I can take a look, I'm going to refactor.

Okay, understood. Can you create a task to track, and set it as blocked on ENG-671 Bidirectional stream for Tunnelbroker?

This revision is now accepted and ready to land.Feb 15 2022, 7:38 PM