Skip to main content
A
Anonymous
November 12, 2008
Question

Netstream publish problem

  • November 12, 2008
  • 1 reply
  • 257 views
Hi,
I am facing a problem to publish and play a live stream from FMS3. I am using flex3 (Action script 3 and FMS 3).
I have coded a demo application with server side script. You can download this application and server side from this URL:
Demo app: http://bang-dev.isprime.com/idma-test/FlashAngels/Amitabh/FMS_Issue/TestAppFMS.zip
Server side: http://bang-dev.isprime.com/idma-test/FlashAngels/Amitabh/FMS_Issue/FMSTest.asc
Please find the issue and let me know, how to fix it.
To change the FMS server string: Go to Src >> Classes >> InitApp.as >> line no 38 and replace your string.
Add a name at left side text field to publish the video.
Add a name at right side text field to play the video.
For the server side, just create a folder inside application folder of FMS with name of “FMSTest” and put the server side “FMSTest.asc “file there.
Let me know incase you face any issue while deploying it.
Thanks,
    This topic has been closed for replies.

    1 reply

    J
    jonpor
    Inspiring
    November 23, 2008
    I haven't tried to run your code, but something obvious is the server-side code. It doesn't do anything.

    When you publish a stream, you need to tell other client to connect to it... manually. There are three thing to account for. A client connecting needs to subscribe to all existing streams. A client connecting needs to inform all existings clients that it has published its stream and give them the stream name so they can subscribe. The client needs to receive stream names of any new (future) connecting clients so it can subscribe to their stream.

    First you need to publish your stream... lets say this is client A and publishes a stream named stream_A.

    1. Then you need to send the stream name (stream_A) to all other existing clients, so they can subscribe to it.
    2. Then you need to receive the names of existing clients streams, so the client can subscribe to them.

    The logic in step 1, will handle any new clients connecting in the future.

    If anyone sees any errors in this or has a better method.. please feel free to add to it....
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices