Remove received datagram buffer from quic/quic_transport.
We've concluded in https://chromium-review.googlesource.com/c/chromium/src/+/2000410 that it would be easier for now to have that buffer in the renderer instead. Therefore, a push-based API without a buffer makes more sense.
gfe-relnote: n/a (not used in GFE)
PiperOrigin-RevId: 290121880
Change-Id: I4bff86e27c1d748cd1aea1f0b17a06c14e67e013
diff --git a/quic/quic_transport/quic_transport_client_session.cc b/quic/quic_transport/quic_transport_client_session.cc
index 6db1e4d..2a75c26 100644
--- a/quic/quic_transport/quic_transport_client_session.cc
+++ b/quic/quic_transport/quic_transport_client_session.cc
@@ -263,25 +263,7 @@
void QuicTransportClientSession::OnMessageReceived(
quiche::QuicheStringPiece message) {
- max_incoming_datagrams_ = std::max<size_t>(
- max_incoming_datagrams_,
- kIncomingDatagramBufferSizeInCwnds *
- connection()->sent_packet_manager().GetCongestionWindowInBytes());
- if (incoming_datagrams_.size() >= max_incoming_datagrams_) {
- return;
- }
-
- incoming_datagrams_.push_back(std::string(message));
- visitor_->OnIncomingDatagramAvailable();
-}
-
-QuicOptional<std::string> QuicTransportClientSession::ReadDatagram() {
- if (incoming_datagrams_.empty()) {
- return QuicOptional<std::string>();
- }
- std::string datagram = std::move(incoming_datagrams_.front());
- incoming_datagrams_.pop_front();
- return datagram;
+ visitor_->OnDatagramReceived(message);
}
void QuicTransportClientSession::OnCanCreateNewOutgoingStream(
