helloVideo app in the O'Reilly book

Ask a Question related to Macromedia Flash Flashcom, Design and Development.

  1. #1

    Default helloVideo app in the O'Reilly book

    Hi guys,
    I am going over the helloVideo app in the O'Reilly book.

    I am having a bit of bother with user disconnecting from the app.
    application.onDisconnect is not triggering till the last user leaves the room.
    So the idPool doesn't get updated.

    I am looking over the book and i cant see anything i missed.

    NetConnection.Connect.Closed
    is returned after nc.close() is called.

    I presume i should be seeing the trace on the application.onDisconnect()and
    that the users_so should be updated triggering a change for every other user
    connected.

    Anyone?

    Thanks
    Paul


    [djdomain] Guest

  2. Similar Questions and Discussions

    1. O'Reilly Book
      After doing the following tutorial (http://www.macromedia.com/devnet/mx/flash/articles/video_player.html) which shows you how to manually update a...
    2. Newbie: Trouble w/ O'Reilly example
      I am trying to work with example code from "Programming PHP" chapter 8. The example is the "Business Listing" application. All the files are in...
    3. #24684 [Opn->Fbk]: PHP 4.3.1 + no longer compatible with O'reilly WebSite Pro 3.0
      ID: 24684 Updated by: edink@php.net Reported By: webmaster at wiseosoftwareinc dot com -Status: Open +Status: ...
    4. #24684 [Opn]: PHP 4.3.1 + no longer compatible with O'reilly WebSite Pro 3.0
      ID: 24684 User updated by: webmaster at wiseosoftwareinc dot com Reported By: webmaster at wiseosoftwareinc dot com Status: ...
    5. #24684 [NEW]: PHP 4.3.1 + no longer compatible with O'reilly WebSite Pro 3.0
      From: webmaster at wiseosoftwareinc dot com Operating system: Win 2000 SP4 PHP version: 4.3.1 PHP Bug Type: CGI related Bug...
  3. #2

    Default Re: helloVideo app in the O'Reilly book

    There's been a problem with server side detection of disconnects since FCS 1.5.
    You'll notice that somtimes the server doesn't respond if the client closes the
    connection, and never fires if the connection is terminated when the connection
    is broken (try pulling your network cabe when connected to FMS... you see that
    FMS sees the client as "still there".

    My solution is to build a set of client server methods to update user status.
    On a 5 second interval, the client calls the server method, which in turn
    updates the client object with a timestamp (in a variable). Every 10 seconds,
    the server method loops through the clients and checks the timestamp. If it's
    more than 10 seconds old, it means the client hasn't updates, so the server
    calls client.disconnect on that client.


    JayCharles Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139