// // Copyright 2015 gRPC authors. // // Licensed under the Apache License, Version 2.0 (the "License"); // you may not use this file except in compliance with the License. // You may obtain a copy of the License at // // http://www.apache.org/licenses/LICENSE-2.0 // // Unless required by applicable law or agreed to in writing, software // distributed under the License is distributed on an "AS IS" BASIS, // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. // See the License for the specific language governing permissions and // limitations under the License. // #ifndef GRPC_SRC_CORE_LIB_RESOLVER_RESOLVER_H #define GRPC_SRC_CORE_LIB_RESOLVER_RESOLVER_H #include <grpc/support/port_platform.h> #include <functional> #include <string> #include "absl/status/status.h" #include "absl/status/statusor.h" #include "src/core/lib/channel/channel_args.h" #include "src/core/lib/debug/trace.h" #include "src/core/lib/gprpp/orphanable.h" #include "src/core/lib/gprpp/ref_counted_ptr.h" #include "src/core/lib/resolver/server_address.h" #include "src/core/lib/service_config/service_config.h" extern grpc_core::DebugOnlyTraceFlag grpc_trace_resolver_refcount; // Name associated with individual address, if available. #define GRPC_ARG_ADDRESS_NAME … namespace grpc_core { /// Interface for name resolution. /// /// This interface is designed to support both push-based and pull-based /// mechanisms. A push-based mechanism is one where the resolver will /// subscribe to updates for a given name, and the name service will /// proactively send new data to the resolver whenever the data associated /// with the name changes. A pull-based mechanism is one where the resolver /// needs to query the name service again to get updated information (e.g., /// DNS). /// /// Note: All methods with a "Locked" suffix must be called from the /// work_serializer passed to the constructor. class Resolver : public InternallyRefCounted<Resolver> { … }; } // namespace grpc_core #endif // GRPC_SRC_CORE_LIB_RESOLVER_RESOLVER_H