Thanks for responding! I don't think that can be the problem,
because the MemberLeft event fires, meaning that the master program
received notification that the member has left. So the UDP packet
must have been sent by the client and received by the master, right?
Anyway, I already tried waiting about 5 seconds to see if the
GetMemberList would be updated, but it apparently never does get
updated.
Tom
On Aug 26, 2006, at 4:16 PM, Phil M wrote:
On Aug 26, 2006, at 4:08 PM, Thomas Moore wrote:
The display properly updates when members join. The problem is
that it does not register members leaving. If I quit one of the
client programs, it properly triggers the MemberLeft event of the
master application, but the member who quit remains in the
GetMemberList, even if ask for the list many seconds after the
member program has quit.
Any insight as to why this might be so? Thanks for any help!
It might be that there is not enough time for the UDP packet to be
sent. If that is the case, then a Timer or something similar could
be used to delay the app from quitting too early.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
-------------------------------------------------------------
This message has been scanned by Postini anti-virus software.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
