Re: NSFileHandle readInBackground vs threading?
Re: NSFileHandle readInBackground vs threading?
- Subject: Re: NSFileHandle readInBackground vs threading?
- From: Kyle Sluder <email@hidden>
- Date: Tue, 08 Nov 2011 22:45:19 -0800
On Tue, Nov 8, 2011 at 9:43 PM, Scott Ribe <email@hidden> wrote:
> I assume by "local socket" you mean either a UNIX domain socket or just a regular TCP socket on the local machine? If so, just using regular read & write calls there's no way for data to be lost & not delivered just because it's consumed slowly. There's something else going on. Either the sending end is discarding data and not even writing it, or the receiving is losing it after reading it.
The kernel only has a certain amount of buffer space dedicated to each
incoming TCP port. If the port gets flooded, it drops packets.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden