Thanks to all who responded. It turns out the issue was the bytesRead
count not being properly updated. The data was actually there...
Thaddeus O. Cooper
([EMAIL PROTECTED])
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post
are you sure the data is being sent? What's on the other end sending
it, is it buffering data and not sending the last 216 bytes?
On Oct 24, 2008, at 2:37 AM, Thaddeus Cooper wrote:
Hi All.
I have an NSInputStream that I've set up on the run loop to read
data from a socket. It's mostly wo
I use different APIs, but I just read until I get a 0 or -1 back for the length.
>Hi All.
>
>I have an NSInputStream that I've set up on the run loop to read data
>from a socket. It's mostly working except that when I am sending it a
>large amount of data (say 30k), the last chunk of data neve
Hi All.
I have an NSInputStream that I've set up on the run loop to read data
from a socket. It's mostly working except that when I am sending it a
large amount of data (say 30k), the last chunk of data never shows up.
I have tried reading 1 byte, 10 bytes and 1024 bytes in the
handleStre
