Ticket #279 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

[beheer] object code uses non-documented variables

Reported by: Michiel.Schok Owned by: arjen
Priority: trivial Milestone: MediaMosa 2.1
Component: Core Version: 2.1.2
Keywords: Cc:
MoSCoW: none Estimated time after impact analysis:
Related to project: none Tested: yes
Accepted: yes Estimated Hours:

Description

When looking at the object code for Windows Media Server, I notice some variables are used which are not documented beneath the box.

Those are {WMA_TICKET_URI}, {IF_EXTERNAL}, but maybe some others are used in different server settings.

Change History

Changed 3 years ago by robert

  • owner set to forgacs
  • status changed from new to assigned

Changed 3 years ago by forgacs

  • owner changed from forgacs to arjen

Changed 3 years ago by MC-arjen

  • status changed from assigned to closed
  • version set to 2.1.2
  • resolution set to fixed

We added the notion of {IF_EXTERNAL}, {/IF_EXTERNAL} and {AUTOPLAY_TEXT} ('autostart').

I am not sure about the naming and correct use of {WMA_TICKET_URI}, so not added yet.

Changed 3 years ago by Michiel.Schok

  • tested changed from no to yes
  • accepted changed from no to yes

I see the extra texts. Great.

{WMA_TICKET_URI} is a strange one indeed. I suspect it has been created to facilitate the following situations:

* when starttime and/or duration is given in the playrequest, an .asx with timings and {ticket_uri} is created. the link to the asx is placed in {wma_ticket_uri}
* else {wma_ticket_uri} gets the value of {ticket_uri}

then the object is created. The source points to the .asx, or to the actual stream.

I guess het {IF_EXTERNAL} has something to do with it...

My 2cts.

Note: See TracTickets for help on using tickets.