mobile: introduce ClientEngineBuilder class #42997
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Commit Message: This PR introduces a new ClientEngineBuilder class. This class is a variant of the existing EngineBuilder class that provides a more configurable bootstrap via its exposed API but is similarly used to create an engine. The ClientEngineBuilder requires the user to provide their own cluster and route configuration, giving the user more control over the client's behavior. This client is not intended to be used in mobile environments and does not provide support for XDS as of now.
Additional Description: N/A
Risk Level: Low - this is a new, separate client and should not affect Envoy or Envoy Mobile.
Testing: Unit and integration are included in this PR. I also conducted manual testing using the client in a staging environment to send requests to an Envoy Server.
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A