Mathis Engelbart

Because of #69 we have to do buffer objects. We should set a limit so as to not buffer objects indefinitely when the application doesn't want to read what it...

These are probably not correctly implemented and used.

Until now, we just ignored the existence of object and group IDs and deferred to the application. It would be nice if the transport implementation could handle reordering on the...

Currently, role parameters are mostly ignored. See https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-03#section-6.3.2

From [draft-ietf-moq-transport-03](https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-03#section-5.1): > Objects MUST NOT be sent for unsuccessful subscriptions, and if a subscriber receives a SUBSCRIBE_ERROR after receiving objects, it MUST close the session with a 'Protocol Violation'.

The implementation in #73 just stops wherever we are. See also: https://github.com/moq-wg/moq-transport/issues/363

It doesn't look nice and duplicates _moq_ in the package import path. Do we even need them as sub-packages at all or can the implementations just live in the root...