The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
AJ Heller ec9451e856 Fix typo in documentation 4 years ago
..
security Replaced grpc::string with std::string 4 years ago
README.md Justify existence of this directory 4 years ago
async_generic_service.h Cleanup generic server contexts 4 years ago
async_stream.h Merge branch 'master' into sync-stream 4 years ago
async_unary_call.h Fix typo in documentation 4 years ago
byte_buffer.h Fix google-explicit-constructor 4 years ago
call.h Revert "Revert "Fold Channel and CompletionQueue from grpc_impl to grpc"" 4 years ago
call_hook.h
call_op_set.h Fix google-explicit-constructor 4 years ago
call_op_set_interface.h
callback_common.h Fix google-explicit-constructor 4 years ago
channel_interface.h Reduce templating for async client unary call codegen 4 years ago
client_callback.h Fix by clang-tidy 4 years ago
client_context.h Fix by clang-tidy 4 years ago
client_interceptor.h Move ClientContext from ::grpc_impl to ::grpc 4 years ago
client_unary_call.h Fix by clang-tidy 4 years ago
completion_queue.h Fix google-explicit-constructor 4 years ago
completion_queue_tag.h
config.h Fix by clang-tidy 4 years ago
config_protobuf.h Updated parse_json.cc to rely on config_protobuf.h for protobuf types 4 years ago
core_codegen.h Fix by clang-tidy 4 years ago
core_codegen_interface.h
create_auth_context.h
delegating_channel.h Fix google-explicit-constructor 4 years ago
grpc_library.h Fix google-explicit-constructor 4 years ago
intercepted_channel.h Fix by clang-tidy 4 years ago
interceptor.h Replaced grpc::string with std::string 4 years ago
interceptor_common.h Fix by clang-tidy 4 years ago
message_allocator.h Add non-experimental:: versions under ifdef 5 years ago
metadata_map.h Replaced grpc::string with std::string 4 years ago
method_handler.h Fix google-explicit-constructor 4 years ago
method_handler_impl.h Fix by clang-tidy 4 years ago
proto_buffer_reader.h Fix by clang-tidy 4 years ago
proto_buffer_writer.h Fix by clang-tidy 4 years ago
proto_utils.h Fix by clang-tidy 4 years ago
rpc_method.h Fix by clang-tidy 4 years ago
rpc_service_method.h Revert "Revert "Move ServerContext from ::grpc_impl to ::grpc"" 4 years ago
serialization_traits.h
server_callback.h Fix by clang-tidy 4 years ago
server_callback_handlers.h Check for nullptr (deser failure) before destructing included request 4 years ago
server_context.h Fix by clang-tidy 4 years ago
server_interceptor.h Revert "Revert "Move ServerContext from ::grpc_impl to ::grpc"" 4 years ago
server_interface.h Fix by clang-tidy 4 years ago
service_type.h Fix by clang-tidy 4 years ago
slice.h Fix google-explicit-constructor 4 years ago
status.h Replaced grpc::string with std::string 4 years ago
status_code_enum.h
string_ref.h Fix google-explicit-constructor 4 years ago
stub_options.h
sync.h
sync_stream.h Merge branch 'master' into sync-stream 4 years ago
time.h Fix google-explicit-constructor 4 years ago

README.md

Welcome to include/grpcpp/impl/codegen

Why is this directory here?

This directory exists so that generated code can include selected files upon which it depends without having to depend on the entire gRPC C++ library. This is particularly relevant for users of bazel, particularly if they use the multi-lingual proto_library target type. Generated code that uses this target only depends on the gRPC C++ targets associated with these header files, not the entire gRPC C++ codebase since that would make the build time of these types of targets excessively large (particularly when they are not even C++ specific).

What should user code do?

User code should not include anything from this directory. Only generated code and gRPC library code should include contents from this directory. User code should instead include contents from the main grpcpp directory or its accessible subcomponents like grpcpp/support. It is possible that we may remove this directory altogether if the motivations for its existence are no longer strong enough (e.g., if most users migrate away from the proto_library target type or if the additional overhead of depending on gRPC C++ is not high).