From: Jordan Bigel <[EMAIL PROTECTED]>
Subject: Re: sdk+jmf
Kevin,
You should really be CC'ing to realforum on these so you can get the
benefit of
everyone's expertise in helping to answer your questions.
The broadcast plugins run in the server's space, not the client. Plugins are
loaded dynamically (both for the server and the client) and the client
executable does not link with any of them.
>try to customerize the testplay so that it can request the Real Server
>for a broadcast. I notice there are sample broadcast plugins but are
I'm not sure what you're after here, but if you are talking about the
difference
between playing back static, encoded data file (ie. myvideo.rm) as compared
to playing back a live audio or video stream (ie. a live broadcast) then there
is no code required on the client side to accomplish this. Just provide the
proper URL to the player/testplay/whatever and it will play.
The server and Producer together work to produce a live broadcast and
their respective documentation should explain how to get that going.
Jordan.
At 11:31 AM 8/18/99 -0400, Kevin Liu wrote:
>
>>
>> We recommend that you use our client side APIs to communicate with
>> the server.
>>
>I have the client (testplay) running on NT and the server (Real Server)
>running on Solaris. I am able to change the server configuration parameters
>from a web browser. I tried the testplay (C++) and it works fine. Now, I
>try to customerize the testplay so that it can request the Real Server
>for a broadcast. I notice there are sample broadcast plugins but are
>these for the server, the client, or both. How should I link the plugins
>with the server and the client? My server is equipped with
>the library files (.so files) for broadcasting.
>-- Kevin
