Skip to main content
H
hardis2003
Participant
December 1, 2009
Answered

Does FMS3.5.2 support the whole URL redirection?

  • December 1, 2009
  • 1 reply
  • 783 views

hi,

  

    I have a question.thanks for helping me.

    1. I entered a url in a video player : rtmp://10.0.0.1/vod/mp4:sample1_1500kbps.f4v

    2. this video doesn't exist in 10.0.0.1 server. it is exist in 10.0.0.2.

    3. the server 10.0.0.1 connect, play, and resource not found.

    4. server 10.0.0.1 know that this video exists in 10.0.0.2 ,then redirect the whole url to 10.0.0.2. such as 

        rtmp://10.0.0.2/vod/mp4:sample1_1500kbps.f4v

    I research the three plug-ins(access, authorization, file), but I can't find a way to solve it. So I want to ask, does FMS 3.5.2 support this redirection?

    Thanks again !

    This topic has been closed for replies.
    Correct answer Asa_-_FMS

    That section feels a little misleading to me - as if you could go all the way to the FMSCore, check if the file is there, and if not then redirect.  That's not true.  You could redirect based on the connect line knowing that the file coming from this request isn't going to be there - but that's a little more sophisticated.  If you go that route, you're likely going to want to URI encode that information into your connect line to make a choice, but then again you might not be able to make that choice in the edge adaptor anyway.  You could also build this logic into the player/server in a few ways, but either way it's a bit of work if the content isn't available at that particular machine.

    Honestly I'd recommend going the ways our majority of customers do.  Either making sure that at connect time they end up in the right place if content is limited per FMS.  Either that or make sure that each FMS can get the entire gamut of content as needed and load balance.  Those are the usual approaches.


    Asa

    1 reply

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    December 1, 2009

    You can't redirect based on a stream not found.  You can redirect from the access adaptor based on connection information - you use the redirect API in access adaptor for that.  I'd recommend that if you can make the choice based on connection line that you use that.  If you can't do so then you may want to consider a system where you can direct a client to the proper FMS for the content based on connection information.

    Asa

    H
    hardis2003Author
    Participant
    December 2, 2009

         Asa, thank you very much. and I hope for your second reply.

         In FlashMediaServer3_WhitePaper_ue_v1.pdf. One section writes as below:

         Flash Media Server 3 now supports stream redirection in RTMP, which behaves much like HTTP
         302 redirection. Tis feature can be enabled by using an access adaptor server-side plug-in, or in
         server-side ActionScript. For example, while using an access adaptor running on an Edge server,
         you could use this redirect method to notify a client that a requested video does not exist in the
         expected location, and pass them a new URI for the stream. It could also be useful for other
         Flash Media Server load-balancing schemes, as well as content organization.

         Can you tell me how to understand these red lines?

         I thought 'redirect' could be implement after 'play' , but in access adaptor, 'redirect' only could be implement afer 'connect'. Am I right?

        

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMSCorrect answer
    Adobe Employee
    December 2, 2009

    That section feels a little misleading to me - as if you could go all the way to the FMSCore, check if the file is there, and if not then redirect.  That's not true.  You could redirect based on the connect line knowing that the file coming from this request isn't going to be there - but that's a little more sophisticated.  If you go that route, you're likely going to want to URI encode that information into your connect line to make a choice, but then again you might not be able to make that choice in the edge adaptor anyway.  You could also build this logic into the player/server in a few ways, but either way it's a bit of work if the content isn't available at that particular machine.

    Honestly I'd recommend going the ways our majority of customers do.  Either making sure that at connect time they end up in the right place if content is limited per FMS.  Either that or make sure that each FMS can get the entire gamut of content as needed and load balance.  Those are the usual approaches.


    Asa

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices