components/grpc_support/README.md - Issue 2273403003: Moving gRPC support interfaces out of cronet and into a new component.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: components/grpc_support/README.md

Issue 2273403003: Moving gRPC support interfaces out of cronet and into a new component. (Closed)

Patch Set: Add README Created 4 years, 2 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1 gRPC Support

	2 ===

	3

	4 This directory contains the interface and implementation of the API to use

	5 an external network stack from gRPC. Chrome is the only current implementor

	6 of this interface, and so gRPC refers to this API as [Cronet] [https://github.co m/grpc/grpc/blob/a8663fa55433732ea0f6e63c2fd586db0ea6f73f/src/core/ext/transport /cronet/client/secure/cronet_channel_create.c].

	7

	8 Internally to Chrome, there will be two different backings of this API. Cronet
	blundell 2016/10/05 11:09:03 I'm confused: you say that this directory contains I'm confused: you say that this directory contains the implementation, and then that there are two implementations, the first of which lives somewhere else. Is the second the one in //components/grpc_support itself? That seems a little confusing. Higher-level: Why is there a need for two implementations? Naively, it seems like Cronet-for-iOS-apps and Chromium could use the same impl, similar to how Cronet consumes //net.
	9 (//components/cronet/ios), which is a library that allows iOS apps access to

	10 the Chromium networking stack, and Chromium proper. Implementation of the later

	11 is currently in progress.

OLD	NEW

« no previous file with comments | « components/grpc_support/OWNERS ('k') | components/grpc_support/bidirectional_stream.h » ('j') | no next file with comments »