Results 1 to 2 of 2

Thread: StartupStreams.xml - affected by Application.xml's Client-->Access node?

  1. #1

    Default StartupStreams.xml - affected by Application.xml's Client-->Access node?

    Hi folks!

    I am using a modified version of your HTTPListener to create, activate, suspend (etc) streams, and have a question for you about mpegts streams which have an entry in StartupStreams.xml. If I suspend one of these streams by setting StreamReadAccess, StreamWriteAccess, SharedObjectReadAccess, and SharedObjectWriteAccess to blank in the stream's Application.xml file, what happens when the server is restarted?

    Does it go ahead and start up the stream because there's a reference to it in StartupStreams.xml, or does it take the Application.xml access settings into consideration and not start the stream?

    Thank you very much!

  2. #2

    Default

    "to blank in the stream's Application.xml file"

    This only happens in memory. The file on disk is not changed. So, when Wowza restarts, it will read the Application.xml from disk.

Similar Threads

  1. Using StartUpStreams.xml
    By kmax1940 in forum General Forum
    Replies: 1
    Last Post: 08-06-2013, 09:05 AM
  2. Access to conf/Application.xml properties
    By azhurb in forum Server-side Modules and Code Samples Discussion
    Replies: 5
    Last Post: 11-29-2011, 07:10 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •