if (!is_metadata_ready_) {I don't think we can simply do this. `is_metadata_ready == true` means all endpoints are ready to start cryptographic handshakes. (See ServiceEndpointRequest::EndpointsCryptoReady).
If we support follow-up HTTPS queries, endpoints may have different states about crypto handshake readyness. Probably we need separate state per endpoint regarding EndpointsCryptoReady, which requires API surface changes. Also, HttpStreamPool::AttemptManager, which uses the API, assumes that once EndpointsCryptoReady() returns true all endpoints are crypto ready. We need to update AttemptManager as well.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (!is_metadata_ready_) {I don't think we can simply do this. `is_metadata_ready == true` means all endpoints are ready to start cryptographic handshakes. (See ServiceEndpointRequest::EndpointsCryptoReady).
If we support follow-up HTTPS queries, endpoints may have different states about crypto handshake readyness. Probably we need separate state per endpoint regarding EndpointsCryptoReady, which requires API surface changes. Also, HttpStreamPool::AttemptManager, which uses the API, assumes that once EndpointsCryptoReady() returns true all endpoints are crypto ready. We need to update AttemptManager as well.
addressed this properly in https://crrev.com/c/7543703 which replaces `is_metadata_ready_` with `https_response_received_` and gates `IsMetadataReady()` on `HasPendingMetadqataTargets()`. it only returns true when all metadata target names have resolved addresses. Abandoning this CL in favor of that one.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Helmut Januschka abandoned this change.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |