Skip to content
Snippets Groups Projects
  1. Nov 16, 2021
    • Josh Soref's avatar
      tests: Spelling fixes · 4fc59ccc
      Josh Soref authored
      Correct typos of the following word families:
      
      mounting
      jitterbuffer
      thrashing
      original
      manipulating
      entries
      actual
      possibility
      tasks
      options
      positives
      taskprocessor
      other
      dynamic
      declarative
      
      ASTERISK-29714
      
      Change-Id: I6b94659d045eec5d8d020fce2e9b6e2f593dfeb6
      4fc59ccc
  2. Apr 12, 2017
  3. Oct 27, 2016
    • Corey Farrell's avatar
      Remove ASTERISK_REGISTER_FILE. · a6e5bae3
      Corey Farrell authored
      ASTERISK_REGISTER_FILE no longer has any purpose so this commit removes
      all traces of it.
      
      Previously exported symbols removed:
      * __ast_register_file
      * __ast_unregister_file
      * ast_complete_source_filename
      
      This also removes the mtx_prof static variable that was declared when
      MTX_PROFILE was enabled.  This variable was only used in lock.c so it
      is now initialized in that file only.
      
      ASTERISK-26480 #close
      
      Change-Id: I1074af07d71f9e159c48ef36631aa432c86f9966
      a6e5bae3
  4. Jul 13, 2015
    • Matthew Jordan's avatar
      media cache: Add a core API and facade for a backend agnostic media cache · 3ea0d383
      Matthew Jordan authored
      This patch adds a new API to the Asterisk core that acts as a media
      cache. The core API itself is mostly a thin wrapper around some bucket
      API provided implementation that itself acts as the mechanism of
      retrieval for media. The media cache API in the core provides the
      following:
       * A very thin in-memory cache of the active bucket_file items. Unlike a
         more traditional cache, it provides no expiration mechanisms. Most
         queries that hit the in-memory cache will also call into the bucket
         implementations as well. The bucket implementations are responsible
         for determining whether or not the active record is active and valid.
         This makes sense for the most likely implementation of a media cache
         backend, i.e., HTTP. The HTTP layer itself is the actual arbiter of
         whether or not a record is truly active; as such, the in-memory cache
         in the core has to defer to it.
       * The ability to create new items in the media cache from local
         resources. This allows for re-creation of items in the cache on
         restart.
       * Synchronization of items in the media cache to the AstDB. This
         also includes various pieces of important metadata.
      
      The API provides sufficient access that higher level APIs, such as the
      file or app APIs, do not have to worry about the semantics of the bucket
      APIs when needing to playback a resource.
      
      In addition, this patch provides unit tests for the media cache API. The
      unit tests use a fake bucket backend to verify correctness.
      
      Change-Id: I11227abbf14d8929eeb140ddd101dd5c3820391e
      3ea0d383
Loading