Re: [webrtc-rtptransport] Make RtpTransport transferable (#33)

I would tend to go with something similar to WebRTC encoded transform.
This removes the need to deal with out of process dedicated workers for instance.
That would mean something like:

```
interface RTCRtpTransport {
  Promise addRtpSendStream(RTCRtpSendStreamInit);
  Promise addRtpReceiveStream(RTCRtpReceiveStreamInit);
  attribute RTCRtpTransportHandler? handler;
}

[Exposed=DedicatedWorker]
interface RTCRtpTransportProcessor : EventTarget {
  attribute EventHandler onrtpsent;
  attribute EventHandler onrtpacksreceived;
  attribute EventHandler onpacketizedrtpavailable;
  sequence<RTCRtpPacket> readPacketizedRtp(maxNumberOfPackets);

  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;
};

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

[Exposed=DedicatedWorker]
interface RTCRtpTransportHandlerEvent : Event {
    readonly attribute RTCRtpTransportProcessor processor;
};

partial interface DedicatedWorkerGlobalScope {
    attribute EventHandler onrtcrtptransport;
};
```



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


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

Received on Wednesday, 26 June 2024 13:06:28 UTC