![]() |
|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Search | Today's Posts | Mark Forums Read |
Gnucleus (Windows) For assistance for users with the Gnucleus program. Important links: Updated Gnucleus 2.2.0.0 Installer! and also Updated Connection Caches for Gnucleus! |
| LinkBack | Thread Tools | Display Modes |
| |||
![]() There are about 10 socket derived classes in gnucleus for a variety of specific purposes. I try to keep the Close() method accross them the same. You're referencing some old code there though, I'm pretty active with updates usually so I suggest going to gnucleus.net, reading the instructions for getting the latest source and checking it out. The current code first locks the thread the socket is being closed in and once it is locked does this: AsyncSelect(0); ShutDown(1); I took the clean receive buffer stuff out of there because it was pointless. There is a huge bug with misdirectedn messages in CAsyncSocket derived classes, but it is fixed by putting AsyncSelect(0); in the deconstructor. It took me sooo long to find that simple fix. |
Thread Tools | |
Display Modes | |
| |
![]() | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Question on Gnucleus sockets, STL | Kaom | Gnucleus (Windows) | 2 | August 20th, 2002 12:08 PM |
Question about Socket error | Unregistered | Support: General | 2 | June 25th, 2002 03:21 PM |
gnucleus.exe will now close | Unregistered | Gnucleus (Windows) | 0 | May 29th, 2002 12:26 AM |
Should LimeWire close when I close the terminal window? | Unregistered | General Linux Support | 4 | September 19th, 2001 07:37 PM |
socket error? | Unregistered | Gnotella (Windows) | 1 | July 15th, 2001 08:31 PM |