- Jan 15, 2016
-
-
David Garcia Quintas authored
-
- Jan 12, 2016
-
-
murgatroid99 authored
-
- Jan 08, 2016
-
-
Craig Tiller authored
-
- Dec 22, 2015
-
-
Craig Tiller authored
-
- Dec 17, 2015
-
-
Jan Tattermusch authored
-
- Dec 15, 2015
-
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
- Dec 11, 2015
-
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
- Dec 10, 2015
-
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
- Dec 09, 2015
-
-
Jan Tattermusch authored
-
- Dec 08, 2015
-
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
- Dec 07, 2015
-
-
Jan Tattermusch authored
-
- Dec 02, 2015
-
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
- Nov 20, 2015
-
-
Julien Boeuf authored
The purpose of this is to be able to install a composition policy that describes which types are incompatible and that will be enforced during call creds composition. If this functionality is wanted it will be done in an additive function in the API like : void grpc_call_credentials_set_composite_policy( grpc_call_credentials_composite_policy policy);
-
- Nov 19, 2015
-
-
Jan Tattermusch authored
-
Julien Boeuf authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
- Nov 18, 2015
-
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-
Jan Tattermusch authored
-