[asterisk-dev] Asterisk 14 - Remote URI Playback

[BJ Weschke]

  Matt -

  This is a pretty neat idea, indeed, but I've got some 
questions/thoughts on implementation. :-)   Apologies if all of this was 
already considered/accounted for already..

  1) Does the entire file need to be downloaded and in place on the HTTP 
Media Cache before you can call an ast_openstream on it? This could 
cause some problems with larger files not sitting on a fat pipe local to 
the Asterisk instance.
  2) What kind of locking is in place on the design to prevent HTTP 
Media Cache from trying to update an expired resource that's already in 
the middle of being streamed to a channel?
  3) I think you need to also introduce a PUT method on HTTP Media Cache 
because I can think of a bunch of scenarios where having a write 
operation on func_curl may be lacking in the file needing to be 
retrieved (eg - trying to pull ACL'd media from an S3 volume where you 
need custom HTTP request headers, etc). We shouldn't try to 
architect/design for all of these scenarios in Asterisk via a write 
operation on func_curl and a PUT to HTTP Media Cache seems like a 
reasonable approach to handle that.

  Thanks!

  BJ

On 11/4/14, 1:09 PM, Matthew Jordan wrote:
> Hey everyone -
>
> One of the action items on the list from AstriDevCon was to flesh out
> some of the ARI feature proposals that had been made for Asterisk 13.
> I've just finished putting together a draft of the first one for
> Remote URI Playback. You can find the proposal page here:
>
> https://wiki.asterisk.org/wiki/display/AST/Asterisk+14+Project+-+URI+Media+Playback
>
> Ben Langfeld has already given some excellent feedback on the proposed
> approach; I'd encourage everyone to chime in on the page as there are
> some interesting edge cases that have to be considered for the
> feature.
>
> If you'd like to participate in the development and/or testing, please
> let me know either by replying to this e-mail or by commenting on the
> wiki page.
>
> Thanks!
>
> Matt
>