TheRealTimeWeb.com

TweetBacks

Comments

• #1 by Aran on 8/7/08 - 12:33 PM

  

  Stefan.
  
  As a moderator o the swfobject project, I will log an issue here ( http://code.google.com/p/swfobject/issues/list ) . Could you please supply me a link to an app / test page which exhibits the behavior?
  
  Cheers,
  Aran

• #2 by Stefan Richter on 8/7/08 - 12:43 PM

  

  yes no problem, could you supply your email or drop me a line at stefan AT flashcomguru.com

• #3 by Jay Charles on 8/7/08 - 1:35 PM

  

  Another interesting thing I noticed in dealing with non-disconnects... tabbed browsing in IE7 also plays a role. I've found that even when using SWFObject v1, having multiple tabs open can also prevent FMS from seeing the client disconnect (open the FMS app page in one tab, open google in another tab, close the FMS tab... no disconnect). If find this to be the case with FMS 2 and 3.
  
  In the end, I'm still using the old "heartbeat" connection checking method in any application that relies on timely detection of clients leaving... seems that's the only bulletproof way of doing it.
  
  Also, I tend to do things to prevent duplicate entires in user lists to account for the "fudge" time I allow in the hearbeat routine. I typically check the userlist object for matches, and then disconnect the client associated with the old entry before adding the new client to the list (sort of how Yahoo IM handles their logins... new client bumps old client). Of course, this assumes that the application requires registration of user names (most of mine do).

• #4 by eitanpo on 8/7/08 - 2:42 PM

  

  i have the same problem on some machines even without swfobject. the swfobject issue is solved by manually closing connection on beforeunload event from the webpage (unload event might not fire)

• #5 by TK on 8/14/08 - 7:45 PM

  

  Is there a huge delay on the onDisconnect firing or not at all? I don't know if this applies, but even when Firefox closes, it still runs for a bit in the background saving session info. Could this be something similar only in IE?

• #6 by Stefan Richter on 8/14/08 - 8:47 PM

  

  not sure, I haven't waited long enough. However closing IE kills the user right away, and fires onDisconnect. The SWFObject guys have more or less confirmed that this may be a bug in the SWFObject cleanup routine it runs when it unloads.

• #7 by Stephen Beattie on 9/8/08 - 5:07 PM

  

  I came up against this too. There is a fix available in the form of a bit of JS to close the connection:
  
  swfobject.addDomLoadEvent( function(){
  swfobject.removeSWF( my_div_id );
  });
  
  Does the trick for me (using SWFObject v2.1 beta7).
  
  Hope this helps.

• #8 by Flug on 9/10/08 - 10:08 AM

  

  Well, this is one more reason not to use the IE. Sorry for that pragmatic way to solve the problem, but that

• #9 by George Kosch on 10/25/08 - 4:29 PM

  

  I have an fms app which won't disconnect people in IE unless they close the browser completely. Simply going to another url in the browser leaves their name in the peoplelist. I've tried everything here without success. Even IE 8 shows same problem on Vista. IE on XP works fine as well as some versions of IE on Vista.
  
  Firefox, opera, chrome all work fine everytime.
  
  The problem, it seems, is IE won't "leave" pages until it's closed no matter what.
  
  Any ideas on this one?

• #10 by Stefan Richter on 10/25/08 - 7:26 PM

  

  Hi George,
  could you email me please (stefan AT flashcomguru.com) and if possible send me your application. Someone at Adobe is looking into the issue and it would help if I had more cases to show them.
  I have one application however which shows this behaviour in other browsers too and I am not yet sure why this is happening.

• #11 by George Kosch on 10/25/08 - 10:12 PM

  

  Here is another example of this issue with Yahoo's live video area at (mine for example) http://live.yahoo.com/georgekosch. I start my video feed and then hit refresh in IE only to have their system tell me that a live video is still on. If I do same with chrome/FF it works fine. System logs me out, then in and I can start video again.
  
  This must be an IE issue with live fms video where the browser "just won't let go" until you close it down completely.
  
  You can get a free account and see for yourself if you have a newer version of IE 7 or beta 8. Again, other workstation with IE (older) is fine.
  
  Stefan, I sent you some stuff on this via hotmail account - just in case it's in your spam folder :)

• #12 by George Kosch on 11/13/08 - 2:49 PM

  

  I got out of bed this morning to a freshly rebooted computer and Bill Gates telling me they had to "apply patches" and....IE disconnects just fine!! Works like a charm.

• #13 by cheinan on 6/14/10 - 3:21 PM

  

  this problam is not connected to SWF on client side it is all about explorer bed behavior.
  this is the final working solution:
  on server side:
  application.onConnect = function(client)
  {
  client.intervalId = setInterval(checkForAlive, 8000, client);
  }
  
  function checkForAlive(client)
  {
  var res = new Object();
  res.client = client;
  res.onResult = function(val)
     {
        client.isCon = 1;
  }
  client.call("checkIsCon", res);
     //trace(client.isCon);
     if(client.isCon == 0)
     {
        application.disconnect(client);
        clearInterval(client.intervalId);
     }
     else
     {
        client.isCon = 0;
     }
  }
  
  on the user swf:
  function checkIsCon()
  {
     return true;
  }
  
  thats it - working like charm...

• #14 by cheinan on 6/14/10 - 3:24 PM

  

  sorry forgot this parameter:client.isCon = 1;
  here the fix:
  application.onConnect = function(client)
  {
  client.isCon = 1;
  client.intervalId = setInterval(checkForAlive, 8000, client);
  }