SIMID:Creative:requestChangeAdDuration args.duration values
andmig opened this issue · 1 comments
Currently, SIMID details SIMID:Creative:requestChangeAdDuration Message.args.duration value -2, which depicts unknown duration and, incidentally, indefinite user experience length. Historically, this is the VPAID legacy.
If the value -2 is the only useful instruction, why do we bother with the message parameters at all? By the same token the naming convention requestChangeAdDuration is not the best descriptor. Perhaps, something along the lines of creativeHandlesAdProgress would be better.
Of course, for the efficiencies reasons, we may want to pretend that, although only value -2 is presently at play, to assure continuity, scalability and support custom player-ad integrations, we leave it at that.
If, however, we seriously consider additional scenarios that necessitate other than -2 values, we may be about to open a floodgate of tough player-side impositions.
There are, at least, two other theoretical scenarios ad duration change may entail:
Scenario 2 - more realistic
Creative increases ad duration to a specific value. For instance, with the initial main media duration 20 sec., creative appends 10 sec. of another video (internally0. Subsequently, the ad is auto-closed upon secondary video completion.
Scenario 1 - more of a borderline case
Creative wishes to shorten the ad. The result is that playback stops prematurely; with all associated consequences.
Discussed. The latest copy reflects the decision.