readonly attributes

[aboba]

In the Editor's draft, we have:

partial interface RTCDtlsTransport {
attribute RTCIceTransport transport;
};

partial interface RTCRtpSender {
attribute RTCDTlsTransport transport;
};

partial interface RTCRtpReceiver {
attribute RTCDTlsTransport transport;
};

Should these attributes be readonly? That is what was proposed today in W3C WEBRTC.

If the desire is to change the transports, shouldn't we have a setter to accomplish this?

[ShijunS]

another similar case is
interface RTCRtpSender {
attribute MediaStreamTrack track;

The "track" attribute should also be read-only. We can define a setTrack method with success and failure callbacks for dynamic track changes, which I expect to be an async operation.

[pthatcher]

I agree it should be readonly. It is in this doc from 12/2013:
https://docs.google.com/a/google.com/document/d/1CSt0M_aX1k9GAdUdKgCn79hCsywur14K5ATSVz3tIiQ/edit#heading=h.jhx5h18mgaw0

But that doc doesn't have setTrack. Is that because we thought we didn't
need it? It seems like we should have setTrack.

On Tue, May 20, 2014 at 12:55 PM, ShijunS notifications@github.com wrote:

another similar case is
interface RTCRtpSender {
attribute MediaStreamTrack track;

The "track" attribute should also be read-only. We can define a setTrack
method with success and failure callbacks for dynamic track changes, which
I expect to be an async operation.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/92#issuecomment-43674806
.

[aboba]

Yet another attribute that should be readonly:

partial interface RTCSctpTransport : RTCDataTransport {
attribute RTCDtlsTransport transport;
}

[aboba]

And yet another one:

[Constructor(optional RTCIceOptions options)]
interface RTCIceListener {
attribute RTCIceOptions? options;
};

For the constructor, should RTCIceOptions be optional (so that we might need a setter) or can we always expect it?

[aboba]

At the June 24, 2014 ORTC CG meeting, consensus was to remove DtlsTransport.setTransport. There's not a really good reason for it, since we have IceTransport.restart now.

[aboba]

Proposed resolution:

partial interface RTCDtlsTransport : RTCStatsProvider {
readonly attribute RTCIceTransport? transport;
};

partial interface RTCRtpSender : RTCStatsProvider {
readonly attribute MediaStreamTrack track;
readonly attribute RTCDtlsTransport transport;
readonly attribute RTCDtlsTransport rtcpTransport;
void setTransport (RTCDtlsTransport transport, optional RTCDtlsTransport rtcpTransport);
void setTrack (MediaStreamTrack track);
};

partial interface RTCRtpReceiver : RTCStatsProvider {
readonly attribute MediaStreamTrack? track;
readonly attribute RTCDtlsTransport transport;
readonly attribute RTCDtlsTransport rtcpTransport;
void setTransport (RTCDtlsTransport transport, optional RTCDtlsTransport rtcpTransport);
};

interface RTCIceListener {
RTCIceOptions getOptions ();
void setOptions (RTCIceOptions options);
};

partial interface RTCSctpTransport : RTCDataTransport {
readonly attribute RTCDtlsTransport transport;
};