>> believe was not supplying any events so the WaitNextEvent was just >> sitting >> there. > >OK, I just caught this. > >As I understand it, the low-level TCP code is supposed to be generating >events that will satisfy WaitNextEvent(). It's possible that the TCP >stack is poorly integrated with Mac OS and is using some other >signalling mechanism. If that's the case, your socket code probably >needs to pick up the slack and provide the necessary glue to feed >packets into the event stream by making the sockets into file handles. >
Well the TCP stack I prefer is MacTCP as OpenTransport is too big for compacts IMO. As I now know the debugger is getting in the way of the Event Mechanism I should hopefully be able to look out for future problems, I'll keep the list posted on my progress. Regards Sean. -- Classic Computing Pages: http://www.megadon.co.uk/syrinx/ -- Compact Macs is sponsored by <http://lowendmac.com/>. Support Low End Mac <http://lowendmac.com/lists/support.html> Compact Macs list info: <http://lowendmac.com/lists/compact.shtml> --> AOL users, remove "mailto:"; Send list messages to: <mailto:compact.macs@mail.maclaunch.com> To unsubscribe, email: <mailto:[EMAIL PROTECTED]> For digest mode, email: <mailto:[EMAIL PROTECTED]> Subscription questions: <mailto:[EMAIL PROTECTED]> Archive:<http://www.mail-archive.com/compact.macs%40mail.maclaunch.com/> --------------------------------------------------------------- iPod Accessories for Less at 1-800-iPOD.COM Fast Delivery, Low Price, Good Deal www.1800ipod.com ---------------------------------------------------------------
