Quoting Matthew Lye <m...@talkwireless.ca> from ml.softs.gtk-gnutella.devel: :Okay, sure. I'd normally be reluctant to offer a patch, but the :changes involved are really pretty simple. :For purposes of archive, note that I mistakenly specified "vendors.c" :earlier in this thread when I of course meant "ban.c"
Your patch ties the ban logic to the Foxy servent name. This is probably not what we want: I'd prefer something that looks for the authentication header in the handshake, regardless of the servent name. In the future, Foxy may remove the header and become fully inter-operable, so hardcoding their name is dangerous. Second, another vendor may choose to do the same thing with another name. Raphael ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
