Re: What causes a kCFStreamEventEndEncountered
Re: What causes a kCFStreamEventEndEncountered
- Subject: Re: What causes a kCFStreamEventEndEncountered
- From: Liwei <email@hidden>
- Date: Mon, 14 Jul 2008 02:13:52 +0800
I'm just using netcat "nc -l 5000" as the server.
I have a feeling that as long as the stream manages to write
everything I've sent it when kCFStreamEventCanAcceptBytes is brought
up, it considers the stream to be at its end. Then it looks like I can
only use streams in a "transactional" way, like how its being used in
CFFTP and CFHTTP.
How then can I use it in a persistent manner?
If not, how can I immediately reopen the streams once they're closed,
continuously trying until it is opened?
I do know that streams cannot be reopened once they're closed, but I
can just dispose of the current stream and recreate one. Is there a
better way? One that does not disturb the read stream?
2008/7/14 Jens Alfke <email@hidden>:
>
> On 13 Jul '08, at 12:49 AM, Liwei wrote:
>
>> So I'm wondering what causes a kCFStreamEventEndEncountered and
>> how does it determine that the stream has ended when I'm the one
>> writing to it?
>
> It means the other peer closed the socket on its end. You might check what's
> going on at the other end; it could be that the process there doesn't like
> the data you're sending it.
>
> —Jens
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden