- From: <bugzilla@jessica.w3.org>
- Date: Wed, 27 Aug 2014 22:46:00 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25920 --- Comment #14 from Mark Watson <watsonm@netflix.com> --- (In reply to David Dorwin from comment #12) > (In reply to Mark Watson from comment #11) > > As per comment #9, the change should not have removed the possibility for > > the CDM to populate the destinationURL field. > > I don't think comment #9 says this. Well, that's what I understood during the discussion of this bug and would certainly have objected at the time if the proposal was to remove the possibility for the CDN to set the destinationURL. Apologies if that was my min-understanding. > > Are there scenarios *not related to initData* that would use destinationURL > in generateRequest()? If so, we should evaluate how they fit in an > interoperable application before adding complexity to support them. The initialization exchange is one. In this case the application may just need a one-bit indication from the CDM as to whether the message is to be sent to the initialization server or the regular application server. The destinationURL can be used for that (this is what I mean about the destinationURL containing information used for routing - it may not be the actual URL, but it can be something which selects from amongst a set of URLs known to the application). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 27 August 2014 22:46:02 UTC