Re: Problem closing CFWriteStream [moved from darwin-dev, as it seems more appropriate here]
Re: Problem closing CFWriteStream [moved from darwin-dev, as it seems more appropriate here]
- Subject: Re: Problem closing CFWriteStream [moved from darwin-dev, as it seems more appropriate here]
- From: Eli Bach <email@hidden>
- Date: Mon, 30 Jun 2008 16:57:38 -0700
On Jun 30, 2008, at 4:17 AM, Quinn wrote:
At 20:07 -0700 20/6/08, Eli Bach wrote:
Yeah, this probably works, but the documentation doesn't explicitly
say that it has sent all data to the kernel (even after you call
CFWriteStreamClose()). I've filed a bug report about this,
Do you have the bug numbers handy? I'd like to check on their state.
but I am surprised that there have only been a couple of mentions
of these issues [handling an orderly close like this, or even a
disorderly close]. The stream networking API is from 10.2 or 10.3,
so the API should handle stuff like this.
My experience is that most developers never think about issues like
this (most of them have never even heard of <x-man-page://8/
shutdown>). Personally, however, I agree that this issue is
important and I'd like to get to the bottom of it.
Bug ID: 6025613
_______________________________________________
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