site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Feb 24, 2010, at 6:15 AM, Hado Hein wrote:
If I send it with CFSocketSendData is the Data afterwards released. The docs don't say this.
In general, if the docs don't specify, it's because things follow the normal ref-counting conventions. I.e. the data is not released. Presumably the implementation either retains or copies it, so you are still in charge of any reference that you own.
If it is not released it should be valid on my next send-cycle. So I'd reuse it, the pointed to data is read again (it mitght have changed in the meantime) and sended out. This is what I'd expect.
This wouldn't work if CFSocketSendData retains the CFDataRef and accesses it later (i.e. if it has to queue it because the socket's write buffer is full.) In that case you might be overwriting bytes that it hasn't sent yet, causing the wrong data to be sent. It would be safer to use a new CFData object every time. —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com