Re: [webrtc-rtptransport] Create RTCRtpTransportProcessor and move high freq fields there (#68)

Here is an iteration of the current API, with the handle/processor pattern & using callbacks instead of events+read:

```
[Exposed=DedicatedWorker]
interface RTCRtpTransportProcessor {
  readonly attribute any options;

  readonly attribute unsigned long bandwidthEstimate;
  readonly attribute unsigned long allocatedBandwidth;
  attribute unsigned long customAllocatedBandwidth;
  attribute unsigned long customMaxBandwidth;
  attribute unsigned long customPerPacketOverhead;

  attribute RTCPacketizedRTPCallback? packetizedRTPCallback;
  attribute RTCSentRTPCallback? sentRTPCallback;
  attribute RTCReceivedRTPAcksCallback? receivedRTPAcksCallback;
}

callback RTCPacketizedRTPCallback = undefined(sequence<RTCRtpPacket> packets);
callback RTCSentRTPCallback = undefined(sequence<SentRtp> sentRtp);
callback RTCReceivedRTPAcksCallback = undefined(sequence<RtpAcks> acts);

[Exposed=Window]
interface RTCRtpTransportProcessorHandle {
  constructor(Worker worker,  optional any options, optional sequence<object> transfer);
}

[Exposed=Window]
partial interface RTCRtpTransport {
  attribute RTCRtpTransportProcessorHandle? processor;
}
```

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/pull/68#issuecomment-2360935074 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 19 September 2024 13:05:27 UTC