Skip to main content
J
jonpor
Inspiring
February 25, 2009
Question

admin consule.. multiple same named clients

  • February 25, 2009
  • 1 reply
  • 298 views
I've a have an audio chat application. Seems to work fine on initial connect. But if a client disconnects and reconnects then I see many cients shown in the admin consule. I don't know if this is a display update issue or a bug (my program or FMS).

For example on intial connect, it all sets up fine:

/componentFramework/NetStreamExtended/instance1/user1
client:ID: Status:
AAAA Publishing: {wed feb 25 00:01 .. }
BBBB Viewing {wed feb 25 00:03.. }

/componentFramework/NetStreamExtended/instance1/user2
client:ID: Status:
BBBB Publishing: {wed feb 25 00:03 .. }
AAAA Viewing {wed feb 25 00:01.. }

If I disconnect one client and reconnect it (i.e. reload the app in the browser), I get repeats of one client with different times:


/componentFramework/NetStreamExtended/instance1/user1
client:ID: Status:
AAAA Publishing: {wed feb 25 00:05 .. }
BBBB Viewing {wed feb 25 00:03.. }

/componentFramework/NetStreamExtended/instance1/user2
client:ID: Status:
BBBB Publishing: {wed feb 25 00:03 .. }
AAAA Viewing {wed feb 25 00:01.. }
AAAA Viewing { web feb 25 00:05 ..}

When ClientA reconnects, Client B shows that is viewing the Client A that disconnected, plus the clientA that reconnected. I'm not sure if I'm seeing a ghost connection or a display refresh error. If it is a ghost connection, what implications does it have and how do I make it go away?

On the same topic, I also have problem with the viewing of streams. After an indefinite period of time, the stream will stop viewing other clients. Is there some sort of time out issue if the pubishing stream remains inactive? There is nothing in the documentation on time outs that I can find.. but then there is very little technical information at all in the documentation... I could probably send a 'keep alive' by sending a message on the net stream every so often but I don't want to do that if this is some other issue.

Any takers on helping me out with this one???
    This topic has been closed for replies.

    1 reply

    J
    jonporAuthor
    Inspiring
    February 25, 2009
    On the topic of the netstream stopping listening .. I put a timer in the clients so they make a netstream.send every minute, so there is always some traffic on the stream. But.. the clients still stop listening. The netstream is setup for audio only, so maybe sending a message doesn't register the stream as active? The server is set NOT to disconnect inactive clients. I have every imaginable error handler that I can find and they don't show anything. The server shows nothing. Is there someway to find WHY? a message? trap an event? anything? as to why the stream stops listening?

    I'm a little at a loss as to how to track this one down. Would someone have a sample of a netstream.client and/or nc.client that has all possible error handlers defined so I know I'm not missing one?? I'm writing in flex 3.0 and using FMS 3.0 but even something in Flash would be a good reference. Everything is running off of the local machine.

    On that note, I'll add one thing I found in flex 3.0 is that sometime Alert.show will raise a sandbox error... but not always. But from what I was seeing, sometimes it will mess with the FMS connections without throwing an error. I took out the Alert.show(s) I was using to help trace my way through the program and a lot of things started working again. I'm not sure exactly why/when, but I'll say "Don't use Alert.show" to trace your way through the program! I use them in some parts of the program, but when they are used event listeners or functions for FMS related calls/errors they seems to produce a random sandbox error.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices