To facilitate for ports I have added two fields to MediaStreamDescriptor: 1) A id (string) field where ports can give MSD an unique id. Needed because the label field is usable for this purpose. 2) An userData field (uint64_t) that can be used for whatever purpose is needed.
Created attachment 140513 [details] Patch
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Comment on attachment 140513 [details] Patch The approach we usually use here is to create an ExtraData object that the client can subclass and use to store extra data on these objects. Take a look at WebURLRequest::ExtraData for an example of how this works.
Created attachment 140710 [details] Patch
Fixed. (In reply to comment #3) > (From update of attachment 140513 [details]) > The approach we usually use here is to create an ExtraData object that the client can subclass and use to store extra data on these objects. Take a look at WebURLRequest::ExtraData for an example of how this works.
Comment on attachment 140710 [details] Patch This looks fine, but please remove the m_id property. It doesn't seem to serve any purpose in WebKit. If the embedder wants to use an ID, it can put one in ExtraData.
Created attachment 140883 [details] Patch
(In reply to comment #6) > (From update of attachment 140710 [details]) > This looks fine, but please remove the m_id property. It doesn't seem to serve any purpose in WebKit. If the embedder wants to use an ID, it can put one in ExtraData. Fixed.
Comment on attachment 140883 [details] Patch Clearing flags on attachment: 140883 Committed r116529: <http://trac.webkit.org/changeset/116529>
All reviewed patches have been landed. Closing bug.