Hello Scott, I could replicate the bug. The bug was introduced due to new WorkDevice class addition. I have fixed the bug. Please test it again.
Regards, Varsha ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: "mailbox" <[EMAIL PROTECTED]> Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> Sent: Sunday, July 21, 2002 12:04 AM Subject: Re: [Kaboodle-devel] Bug Report, 20 July > VK: > One more datapoint: if I restart Kaboodle, the > inactive device does get correctly put into the "known > but inactive" device list which gets ping'd regularly, > and the GUI updates as it should. > > To clarify further, I can see from the network > traffic that Kaboodle has two ping lists: "known and > active devices" which get ping'd roughly every 15 > seconds, and "known but inactive" which get ping'd > roughly every 20 seconds. This is good. > > -Scott > > > On Sat, 20 Jul 2002, Scott C. Best wrote: > > > VK: > > Just to confirm: > > > > > One quick bug report, then some replies: devices in > > > the GUI don't go inactive anymore. I can see in the network > > > traffic that the inactive status has been detected, but the > > > deactivation of the icon isn't currently happening. > > > > I'm seeing this problem still, today. My GUI is > > showing 8 devices, but the network traffic is showing only > > 6 devices being ping'd every 5 seconds. It should be seven > > (the Kaboodle machine shouldn't ping itself). Somehow, one of > > the "known devices" fell out of the "ping list" without the > > GUI being updated to show that the device went inactive. > > This doesn't happen all the time, but it does happen. > > > > As you know, a "known device" should stay in the > > "ping list" so that when it comes back, we can detect it > > quickly. > > > > Perhaps, as a safety check, we can have Kaboodle > > rebuild the "ping list" when the user hits "Refresh". This > > way we can be sure that what's shown in the GUI is the > > current status of the devices on the LAN. > > > > thanks, > > Scott > > > > > > > > Now for replies: > > > > > > > > Hello! Sorry about the delay in replying. Speaking > > > > > of delays...the latest version of the Kaboodle sniffer seems > > > > > to have slowed down again. Did your "timing adjustments" on > > > > > the ARP sniffing get undone somehow? > > > > > > > > No. Actually the other code changes to NID in this week shouldn't > > > > affect the sniffer code. > > > > > > The performance I mentioned may have been related to > > > the bugs fixed late this week. Which is to say, the discovery > > > thread was working well today. > > > > > > > > As for your question: > > > > > > > > > > > > > > > 3. At startup, Kaboodle should check to see if another PC > > > > > > > > > > on the LAN is running Kaboodle. If it is, it should get > > > > > > > > > > the NID from that PC, and *not* re-run its own network > > > > > > > > > > discovery. Right now, every PC runs its own LAN discovery, > > > > > > > > > > and sometimes they come up with different answers. > > > > > > > > > > > > What should happen for the Group index and icon index in the above > > > > > > scenario? For e.g say On PC1, I change the group of some PC (xyz) on > > > > > > my LAN to Macintosh group. Then I started Kaboodle on PC2. In this > > > > > > case PC (xyz) will belong to which group on PC2? > > > > > > > > > > The way I see it, there should be a unique NID for the > > > > > whole network, not one per PC. So if I put PC1 into the Macintosh > > > > > group, it should move into that icon group for every Kaboodle > > > > > instance on the LAN *and* for any Kaboodle's that are VPN'd > > > > > with this network. > > > > > > > > > Does this mean that the kaboodle GUI and device properties of all type > > > > of devices on each machine on LAN should be exactly identical? > > > > > > > > > Yes, I think it has to be this way. I cannot think of a good > > > model where the GUI's a device properties are only "partially" identic al. > > > > > > Think of it in the context of a Kaboodle VPN: if I am engaged > > > with other Kaboodle users, and they make changes to their GUI or device > > > properties, when should my GUI update? When the changes are made to the > > > VPN master, or to any node? Gets confusing quickly. The easiest answer is: > > > every LAN has a unique NID. Any changes to the Kaboodle GUI or a device's > > > are recorded in the NID. NID's are propagated ASAP to all Kaboodle parties > > > displaying that NID in a GUI. > > > > > > > > > > Could you please explain me the following > > > > 1. What should happen in case of group additions and deletions? > > > > 2. What should happen on device property change? > > > > 3. What should happen if some kaboodle instance detects the new device? > > > > The current code does not pass the device ID during exchanging the NID > > > > information and if we want the exact NID information to be displayed in each > > > > instance of the kaboodle on the LAN then we need to add this capability of > > > > keeping unique device_ID on a LAN. Is this adequate? > > > > > > If I make a group additions or deletion on PC1, it should first > > > be recorded in the Kaboodle NID on PC1. This change should then be > > > propagated to all Kaboodle devices via the NID synchronization thread. > > > All device property changes should be propagated similarly to all Kaboodle > > > devices via NID synchronization. > > > > > > As far as a unique device_ID, we definitely need one. Any Kaboodle > > > device in the world should be referencable by using first a Network_ID > > > and then a Device_ID local to that network. So if I'm VPN'd with 5 other > > > users, and each has 10 devices on their LAN, I might be able to initiate > > > a VNC connection to "Network-3_Device-5". > > > > > > Hope this helps. Have a good weekend! > > > > > > cheers, > > > Scott > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Kaboodle-devel mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel > > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Kaboodle-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Kaboodle-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
