| commit | e871e9aecb3d7fde31c3ed4388248ad9d77450ea | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Wed Apr 24 09:47:15 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 24 09:48:50 2024 -0700 |
| tree | faa0e1809043ec3c0ee7cbc7862750c59292d3d0 | |
| parent | ee429dd8e97c8bcc4d4373847f7a982f6fb14da5 [diff] |
Wire up xRPC client to talk to Phosphor This CL introduces an xRPC (go/xrpc-in-gmscore-doc) client to talk to Phosphor and connects it to the serivce Binder stub effectively providing the end to end data flow of the module. Currently only the getInitialData() method is added. Once this CL is in, the same will be replicated for authAndSign(). Using xRPC is the recommended way to communicate with 1P services and is cleaner than handrolling a GMSCoreNetworkEngine to send HTTP requests. I verified with laskey@ that Phosphor supports direct GRPC requests. A unit test has been added that spins up an in-process GRPC fake server and currently runs a test against it. Tested end to end with the real Phosphor server locally and I was able to get the correct response. #blindauth PiperOrigin-RevId: 627759698
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.