Hello Scott. FIRST. The GetEngaged implemented as you asked: If a PC isn't a "Master Node" when GetEngaged start, then it shows a MessageBox: *This PC isn't a "Master Node"* *Continue a registration ?*. There are two buttons "YES\NO". If a user pushes "YES" then the registration continues.
SECOND. There is a problem with implementation of your things #1, #2 and #3. That implementation requires an adding of array variable-length data into the structure _NID_DEVICE_ATTRIBS. The Problem is concluded in that the structure _NID_DEVICE_ATTRIBS is used in style C language, rather then in style C++ language. There is no a copy construction and is no some kind of serialization as member of that structure in the source code. Instead of these there is broadly used an operation of direct adduction of address a non-typified memories to pointer on structure and an operation of direct copying a non-typified to memories by size sizeof(_NID_DEVICE_ATTRIBS). All above things don't allow simply insert the array variable-length data into the structure. There isn't a problem to add both the copy construction and the serialization as member of that structure. Problem is concluded in changing of all *an operation of direct adduction of address a non-typified memories to pointer on structure* on *a copy construction* and all *and an operation of direct copying a non-typified to memories* on *serialization as member of that structure*. There are very many such places in the source code (around several hundreds). This work will require plenty of debugging. The problem becomes complicated that this work cannot execute by parts. I expect that this work require approximately week of time. Please let me to know if I must execute above work. - Igor ----- Original Message ----- From: "Igor Kotelevsky" <[EMAIL PROTECTED]> To: "Scott C. Best" <[EMAIL PROTECTED]> Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> Sent: Thursday, October 03, 2002 5:10 PM Subject: Re: Master node > Hello Scott. > I'll implement your things #1, #2 and #3. > Also I'll implement a modification of GetEngaged.exe: > > ...Perhaps we should modify > > GetEngaged.exe instead, to warn users when they install a Partnership > > file into a non-Master Kaboodle instance. > - Igor > > ----- Original Message ----- > From: "Scott C. Best" <[EMAIL PROTECTED]> > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > Sent: Wednesday, October 02, 2002 11:29 PM > Subject: Re: Master node > > > > Igor: > > > > > Hello Scott. > > > A. About *ping*. > > > The things you asked implemented: > > > > The Kaboodle Master Node handles all of these types. The > > > > non-Master nodes should do *only* #3, the Refresh button pings. > > > > Thanks! > > > > > B. About *"Connect" button*. > > > You asked: > > > > Would it be possible that the "Connect" button still works, > > > > but only Partnerships that are known the Master Node can be initiated? > > > I don't see how that can be implemented. > > > > You could do it like this: > > > > 1. The partnerships listed in "Remote Networks" would be the same > > for every Kaboodle instance on the LAN: it would be NID sync'd > > data taken from the Kaboodle Master Node. It would *not* be taken > > from locally installed Partnership files except in the case of > > the Master Node. > > > > 2. If a user looks at the partnerships in "Remote Networks" using a > > non-Master node, it would read: "These are the Partnerships > > currently installed on "Dad's PC", the current Kaboodle Master". > > > > 3. Any Kaboodle instance on the LAN could initiate the VPN connection > > using intra-Kaboodle messaging. That is, a non-Master node would > > signal the Master-Node to initiate a VPN. > > > > > Now the "Remote Networks" tab works as following. > > > If Kaboodle isn't a "Master Node", then only button "Create New > Partnership" > > > is grayed out > > > and the tab has the text > > > *This PC is not a* > > > *"Master Node",* > > > *so the button* > > > *"Create New Partnership"* > > > *is grayed out* > > > > I don't think this is a good idea anymore. I want users to > > be able to create Partnerships easily. Perhaps we should modify > > GetEngaged.exe instead, to warn users when they install a Partnership > > file into a non-Master Kaboodle instance. > > > > > > -Scott > > > > > > > > > ----- Original Message ----- > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > Sent: Tuesday, October 01, 2002 11:25 PM > > > Subject: Re: Master node > > > > > > > > > > Igor: > > > > Sorry, I should clarify: > > > > > > > > > A. About *ping*. > > > > > At Tuesday, October 01, 2002 4:45 AM you wrote: > > > > > > > > 1. When Kaboodle starts up, it asks the LAN for a NID. If > > > > > > > > it doesn't get one, it builds one *and* it sets itself > > > > > > > > as the Master Node. Correct? > > > > > > > When Kaboodle starts up, it asks the LAN for a NID > > > > > > > *only* if it's Master Node. > > > > > > > > > > > > Actually, Kaboodle should always ask the LAN for a NID > > > > > > when it starts up. It should not matter if it's the first time > > > > > > or the seventh time. > > > > > > > > > > > > > > 2. When I hit "Refresh" on a PC that's not the Master Node, > > > > > > > > it still pings all of the Class-C's that it knows about. > > > > > > > > Correct? > > > > > > > When I hit "Refresh" on a PC that's not the Master Node, > > > > > > > it didn't pings at all. > > > > > > > > > > > > It should. A non-Master Kaboodle should ping the LAN when > > > > > > the user hits "refresh". > > > > > I implemented things #1, #2 as your asked. > > > > > At Wednesday, September 25, 2002 9:36 AM you wrote: > > > > > > ...Only the master node pings... > > > > > > > > Kaboodle has four "types" of pings: > > > > > > > > 1. When Kaboodle starts up, if it fails to get a NID from the LAN, > > > > it pings all of the Class-C's it can auto-detect (and it sets > > > > itself as the Master Node). > > > > > > > > 2. When a new device is "sniffed" and is added to the NID, the > > > > Kaboodle Master Node should ping all of the Class-C subnets > > > > it knows about. > > > > > > > > 3. When the user hits Refresh in Kaboodle, that Kaboodle instance > > > > should ping all of the Class-C subnets it knows about. > > > > > > > > 4. Every 5 seconds, the Kaboodle Master Node should ping the > > > > devices known to be in its "active list" to see if they're > > > > still active. > > > > > > > > The Kaboodle Master Node handles all of these types. The > > > > non-Master nodes should do *only* #3, the Refresh button pings. > > > > > > > > > > > > > B. About *restart*. > > > > > At Friday, September 27, 2002 8:11 PM you wrote: > > > > > > Sounds good except for the "after PC restarts" idea. > > > > > > Since it's just a NID status setting, I don't think > > > > > > a restart is required at all. If a VPN is active, the user > > > > > > should get a message saying "The Master Node status will be > > > > > > changed after your GetEngaged partner disconnects". If there > > > > > > is no VPN active, the switch should happen immediately. > > > > > These things are implemented. > > > > > > > > Thanks! > > > > > > > > > Also I implemented following. > > > > > If PC is not a "Master Node", > > > > > then both buttons "Connect" and "Create New Partnership" > > > > > on the "Remote Networks" tab are grayed out and that tab has > > > > > the text > > > > > *This PC is not a* *"Master Node",* > > > > > *so both buttons "Connect" and "Create* > > > > > *New Partnership" are* *grayed out* > > > > > Please let me know what you think about that. > > > > > > > > I'm not sure about this. Would it be possible that the > > > > "Connect" button still works, but only Partnerships that are known > > > > to the Master Node can be initiated? > > > > > > > > > C. ZeBeDee bug. > > > > > I see a bug (both Win2000 and Win98): > > > > > - I try to make remote network connection. > > > > > - I didn't have ZeBeDee component on both Kaboodles. > > > > > - I push the button "Connect" in "Remote Networks" tab. > > > > > - I see the MessageBox > > > > > *Sorry... Kaboodle could not start Zebedee on your PC. This > connection > > > > > will be in View-Only"...* > > > > > - After that I get "debug assertion failed" > > > > > - Kaboodle crash > > > > > > > > Yup, that's a bug. :) > > > > > > > > -Scott > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > > > Sent: Tuesday, October 01, 2002 4:45 AM > > > > > Subject: Re: Master node > > > > > > > > > > > > > > > > Igor: > > > > > > > > > > > > Heya. Some quick feedback: > > > > > > > > > > > > > > Since it's just a NID status setting, I don't think > > > > > > > > a restart is required at all. If a VPN is active, the user > > > > > > > > should get a message saying "The Master Node status will be > > > > > > > > changed after your GetEngaged partner disconnects". If there > > > > > > > > is no VPN active, the switch should happen immediately. > > > > > > > > > > > > > > I'll implement above. > > > > > > > > > > > > Thanks. > > > > > > > > > > > > > > 1. When Kaboodle starts up, it asks the LAN for a NID. If > > > > > > > > it doesn't get one, it builds one *and* it sets itself > > > > > > > > as the Master Node. Correct? > > > > > > > When Kaboodle starts up, it asks the LAN for a NID > > > > > > > *only* if it's Master Node. > > > > > > > > > > > > Actually, Kaboodle should always ask the LAN for a NID > > > > > > when it starts up. It should not matter if it's the first time > > > > > > or the seventh time. > > > > > > > > > > > > > > 2. When I hit "Refresh" on a PC that's not the Master Node, > > > > > > > > it still pings all of the Class-C's that it knows about. > > > > > > > > Correct? > > > > > > > When I hit "Refresh" on a PC that's not the Master Node, > > > > > > > it didn't pings at all. > > > > > > > > > > > > It should. A non-Master Kaboodle should ping the LAN when > > > > > > the user hits "refresh". > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > On Fri, 27 Sep 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > "Master node" implemented as following: > > > > > > > > > 1. Only the master node pings. > > > > > > > > > 2. Only the master node connects with Gnutella to the > GetEngaged > > > > > > > servers. > > > > > > > > > 3. A user can change the "Master node" status (on/off) in > the > > > bottom > > > > > > > part of > > > > > > > > > "System Info" tab. > > > > > > > > > 4. That changing will take effect after PC restarts. > > > > > > > > > A user'll see a respective MessageBox - > > > > > > > > > *Your settings will take effect after PC* > > > > > > > > > *<PcName> restarts*. > > > > > > > > > 5. The "Master node" status is a part of NID data. > > > > > > > > > A user can see and change that status as for itself as for > > > others > > > > > PC's. > > > > > > > > > > > > > > > > > > - Igor > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > > > > Cc: <[EMAIL PROTECTED]> > > > > > > > > > Sent: Wednesday, September 25, 2002 9:36 AM > > > > > > > > > Subject: Re: 21 Sept bug report > > > > > > > > > > 1. The "master node" setup. Only the master node pings. > Only > > > > > > > > > > the master node connects with Gnutella to the > GetEngaged > > > > > > > > > > servers. Registration and Partnership files only need > to > > > > > > > > > > be installed on the master node. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- 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
