RTMPClient: how to play() content from the server

Hi,
   I'm trying to use the new RTMPClient/StreamingProxy
framework to play() a live stream from a master-Red5,
into a slave-Red5 server. I'm unable to figure how
can one get access to incoming audio/video packets
on the stream.

   Here is what I've thought so far .. would
appreciate any feedback/hints.

   * Current streaming-proxy code is meant to publish
     (implements IPushableConsumer)
   * I need to create another class (or add to
StreamingProxy)
     to implement IPullableProvider
   * I can then bridge the proxy into an existing pipe
     on the slave server by doing IPipe.subscribe(proxy)

  Does this look reasonable? How do I get access to
raw RTMP messages coming into the client, so I can
expose them through pullMessage()?

   Is there any other mechanism to achieve this?

Thanks,
Atul

NOTE: I specifically need to use play() ... the
master cannot initiate a broadcast to the slave
(firewall, business-logic, etc). That works
perfectly fine with the latest trunk!



_______________________________________________
Red5 mailing list
Red5osflash.org

http://osflash.org/mailman/listinfo/red5_osflash.org

Would the edge / origin solution do what you need ?

On 27/03/2008, at 10:47 PM, Atul Narkhede wrote:

> Hi,
>   I'm trying to use the new RTMPClient/StreamingProxy
> framework to play() a live stream from a master-Red5,
> into a slave-Red5 server. I'm unable to figure how
> can one get access to incoming audio/video packets
> on the stream.
>
>   Here is what I've thought so far .. would
> appreciate any feedback/hints.
>
>   * Current streaming-proxy code is meant to publish
>     (implements IPushableConsumer)
>   * I need to create another class (or add to
StreamingProxy)
>     to implement IPullableProvider
>   * I can then bridge the proxy into an existing pipe
>     on the slave server by doing
IPipe.subscribe(proxy)
>
>  Does this look reasonable? How do I get access to
> raw RTMP messages coming into the client, so I can
> expose them through pullMessage()?
>
>   Is there any other mechanism to achieve this?
>
> Thanks,
> Atul
>
> NOTE: I specifically need to use play() ... the
> master cannot initiate a broadcast to the slave
> (firewall, business-logic, etc). That works
> perfectly fine with the latest trunk!
>
>
>
> _______________________________________________
> Red5 mailing list
> Red5osflash.org
> 
http://osflash.org/mailman/listinfo/red5_osflash.org


_______________________________________________
Red5 mailing list
Red5osflash.org

http://osflash.org/mailman/listinfo/red5_osflash.org

   Well, I'm not sure. The slave-server is behind
a firewall, and it has control over what streams
can be safely published outside the firewall to
the external world.

Does the edge/origin config handle this?
   - edges not reachable from origin directly
   - edges enforcing invidual access control
    (rather than at origin via RTMPT)


- Atul

> Would the edge / origin solution do what you need ?
> 
> On 27/03/2008, at 10:47 PM, Atul Narkhede wrote:
> 
>> Hi,
>>   I'm trying to use the new
RTMPClient/StreamingProxy
>> framework to play() a live stream from a
master-Red5,
>> into a slave-Red5 server. I'm unable to figure how
>> can one get access to incoming audio/video packets
>> on the stream.
>>
>>   Here is what I've thought so far .. would
>> appreciate any feedback/hints.
>>
>>   * Current streaming-proxy code is meant to
publish
>>     (implements IPushableConsumer)
>>   * I need to create another class (or add to
StreamingProxy)
>>     to implement IPullableProvider
>>   * I can then bridge the proxy into an existing
pipe
>>     on the slave server by doing
IPipe.subscribe(proxy)
>>
>>  Does this look reasonable? How do I get access to
>> raw RTMP messages coming into the client, so I can
>> expose them through pullMessage()?
>>
>>   Is there any other mechanism to achieve this?
>>
>> Thanks,
>> Atul
>>
>> NOTE: I specifically need to use play() ... the
>> master cannot initiate a broadcast to the slave
>> (firewall, business-logic, etc). That works
>> perfectly fine with the latest trunk!
>>
>>
>>
>> _______________________________________________
>> Red5 mailing list
>> Red5 at osflash.org
>> 
http://osflash.org/mailman/listinfo/red5_osflash.org

_______________________________________________
Red5 mailing list
Red5osflash.org

http://osflash.org/mailman/listinfo/red5_osflash.org