Remove unnecessary tests from MoqtSessionTest. Putting the logic in OutgoingSubgroupStreamTest and SubscriptionPublisherTest is more compact and cleaner conceptually.
Includes a small fix to allow opening several streams at once.
Here is a mapping of the deleted tests and what covers them:
OSST = OutgoingSubgroupStreamTest
SPT = SubscriptionPublisherTest
CreateOutgoingSubgroupStreamAndSend -> CreateStream via
SPT::UpdatePriorityWithActiveStreams
FinDataStreamFromCache -> OSST::OnCanWriteSetsAlarm
SendFragmentedObject -> OSST::SendFragmentedObject
GroupAbandonedNoDeliveryTimeout -> SPT::OnGroupAbandonedTooFarBehind
GroupAbandondedDeliveryTimeout is the same as GroupAbandonedNoDeliveryTimeout. This is an identical test!
GroupAbandoned -> SPT::OnGroupAbandonedWithStreams
LateFinInDataStream -> OSST::Fin
SeparateFinForFutureObject -> OSST::FinForFutureObject
PublisherAbandonsSubgrpup -> SPT::OnSubgroupAbandonedWithStream
UnidirectionalStreamCannotBeOpened ->
SPT::OnNewObjectAvailableStreamCreationBlocked,
SPT::OnCanCreateNewUniStreamSuccess
QueuedStreamIsCleared -> SPT::OnCanCreateNewUniStreamSuccess,
SPT::OnCanCreateNewUniStreamPendingCleanup
OutgoingStreamDisappears -> SPT::OnDataStreamDestroyed
SendDatagram -> SPT::OnNewObjectAvailableDatagram
QueuedStreamsOpenedInOrder -> SPT::PendingStreamsInOrder
StreamQueuedForSubscriptionThatDoesntExist ->
SPT::OnCanCreateNewUniStreamPendingCleanup
QueuedStreamPriorityChanged -> MoqtSessionTest::UpdateTrackPriority,
SPT::PendingStreamsInOrder,
SPT::UpdatePriorityWithPendingStreams
DeliveryTimeoutExpiredOnArrival -> OSST::OnCanWriteTimeout
DeliveryTimeoutAfterIntegratedFin -> OSST::OnCanWriteSetsAlarm
DeliveryTimeoutAfterSeparateFin -> OSST::Fin
DeliveryTimeoutAlternateDesign -> AlternateDeliveryTimeout
IncomingRequestUpdateTruncatesSubscription ->
MoqtSessionTest::IncomingRequestUpdateTriggersRequestOk,
MoqtSessionTest::IncomingRequestUpdateTriggersRequestError,
SPT::IncomingUpdateTruncatesSubscription
PiperOrigin-RevId: 918686567
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.
QUICHE has binaries that can run on Linux platforms.
Follow the instructions to install Bazel.
sudo apt install libicu-dev clang lld cd <directory that will be the root of your quiche implmentation> git clone https://github.com/google/quiche.git cd quiche CC=clang bazel build -c opt //... ./bazel-bin/quiche/<target_name> <arguments>
There are several targets that can be built and then run. Full usage instructions are available using the --helpfull flag on any binary.
Usage: quic_packet_printer server|client <hex dump of packet>
Usage: crypto_message_printer_bin <hex of message>
Usage: quic_client <URL>
quic_server: listens forever on --port (default 6121) until halted via ctrl-c.
masque_client: tunnels to a URL via an identified proxy (See RFC 9298).
Usage: masque_client [options] <proxy-url> <urls>
Usage: masque_server
web_transport_test_server: a server that clients can connect to via WebTransport.
moqt_relay: a relay for the Media Over QUIC transport for publishers and subscribers can connect to.
Usage: moqt_relay