Hello Scott. Your thing implemented: Kaboodle saves the IP address after successful remote connection in the registry. When it next try to connect with that partner, it try that IP address *first*, on port 4182, bypassing a Gnutella completely. If it fails to connect, then it returns back to the Gnutella search. All my changes are in the CVS server.
Also I want to notice following my estimation: 1. Current design of source code not very well to answer the purpose of the current functionality of the application. There are very many big functions, which has fuzzy functionality. 2. Source code has very little documentation. 3. There is a big part of code, which was written in style C language, but not in style C++ language. 4. Indications of many variables look as in "hungarian notation", but these real types not conform to that notation. 5. Indications of some variables written in MFC style, others variables don't has that style, even when both of them refer to one class. Things #1 - #5 greatly obstruct further accompaniment and development of the application. - Igor ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: "Igor Kotelevsky" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 10:35 PM Subject: Re: [Kaboodle-devel] Re: VPN bug > Igor: > Sorry, didn't see this email until after I sent my > email describing the LAN traffic. Am looking forward to you > getting to work on this tomorrrow. > > -Scott > > On Mon, 11 Nov 2002, Igor Kotelevsky wrote: > > > Hello Scott. > > > > First. > > The bug you wrote fixed: > > > > Looking at my LAN traffic after I hit the "Connect" > > > > button, I'm not sure that the discovery is working. I don't > > > > see any traffic exchanged between the two endpoints. > > > > Second. > > Now Kaboodle saves the IP address of the latest successful remote connection > > in the registry. > > Please see the registry key > > *SOFTWARE\Kaboodle\LatestRemoteConnections*. > > It didn't tries that IP addresses *first*, on port 4182, > > bypassing Gnutella completely. > > I'll implement that later on (I hope this will tomorrow). > > > > - Igor > > > > > > ----- Original Message ----- > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Sent: Monday, November 11, 2002 10:11 AM > > Subject: Re: [Kaboodle-devel] Re: VPN bug > > > > > > > Igor: > > > Heya. Hope you had a good weekend. Quick questions: > > > > > > 1. Any progress on the update to Kaboodle to use Partner IP > > > addresses as described below? > > > > > > 2. Any progress on the Master Node ping problem? > > > > > > thanks, > > > Scott > > > > > > On Wed, 6 Nov 2002, Scott C. Best wrote: > > > > > > > Igor: > > > > Looking at my LAN traffic after I hit the "Connect" > > > > button, I'm not sure that the discovery is working. I don't > > > > see any traffic exchanged between the two endpoints. What I > > > > *do* see is the request to Gnutella.GetEngaged.Net, and then > > > > multiple requests to the IP address in the Partnership file. > > > > Then, in my VPN status window, that IP address is now shown > > > > as a Gnutella server with a "Handshake OK" status. > > > > > > > > Here's what I think: every time I successfully make > > > > a connection to a VPN partner, I should put their IP address > > > > into a file, or registry entry. When I next try to connect > > > > with them, I should try those IP addresses *first*, on port > > > > 4182, bypassing Gnutella completely. If they fail to connect, > > > > I should fall back to a Gnutella search. > > > > > > > > Of course, the first time I connect with a Partner, > > > > I won't have such a file or registry entry. In that case, I > > > > should use the IP address in the Partnership file first. If > > > > that fails, then fallback to Gnutella. > > > > > > > > Importantly: those IP address I try should *not* end > > > > up in the list of Gnutella servers. I should not see any traffic > > > > to port 4183 except to machines in the list of Gnutella servers. > > > > > > > > hope this helps, > > > > > > > > Scott > > > > > > > > On Wed, 6 Nov 2002, Igor Kotelevsky wrote: > > > > > > > > > Hello Scott. > > > > > I continue VPN bug debugging process. > > > > > I know that Kaboodle receives remote network data, > > > > > which is *exactly* correct, but GUI 'don't want' to show that data. > > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by: See the NEW Palm > > > > Tungsten T handheld. Power & Color in a compact size! > > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > > > > _______________________________________________ > > > > 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
