Thanks for responding. Yes, I thought of this. But the
UpdateMemberList actively queries the web to see who is there and who
is not. This is not *really* what I want to have happen. I assumed
that when someone unregisters from the group, the other group
members' GetMemberList gets updates automatically. If not, what
exactly does Unregister do? The Register method seems to update the
list provided by GetMemberList: why doesn't the Unregister method do
the same? I'm confused...
Anyway, I tried what was suggested and it does not seem to help. In
fact, caused further funky and unexpected behavior that I have not
fully processed yet, though I might have made an error in another way
or not waited long enough.
Best wishes, Tom
On Aug 27, 2006, at 2:36 PM, Tim Hare wrote:
From the Language Reference:
"If you would like a list of the currently connected members, you
can get an
array of their IPs by calling the GetMemberList method. You can
refresh the
list by calling the UpdateMemberList method. It clears the internal
list of
connected members and re-queries the network for members."
After the initial GetMemberList, use UpdateMemberList.
Tim Hare
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Charles Yeomans
Sent: Saturday, August 26, 2006 11:03 PM
To: REALbasic NUG
Subject: Re: Autodiscovery problem
I think the AutoDiscovery class has a method for rebuilding the
member list.
Charles Yeomans
On Aug 27, 2006, at 12:28 AM, Thomas Moore wrote:
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>
_______________________________________________
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>
