Re: CFSocket client side exc_bad_access
Re: CFSocket client side exc_bad_access
- Subject: Re: CFSocket client side exc_bad_access
- From: "Quinn \"The Eskimo!\"" <email@hidden>
- Date: Thu, 20 Mar 2014 08:57:14 +0000
On 19 Mar 2014, at 15:38, Jeremy Thompson <email@hidden> wrote:
> I patching up some even older software that was running on Open Transport.
> The software is a mixture of C and pascal using the Carbon libraries.
> Getting rid of OT and moving to something else will help us garner the
> time for a true ground up re-write. So far running CFSockets have shown
> the best results when having to deal with a single threaded legacy
> application with Carbon. Traditionally I like to program with BSD sockets
> and libevent. I've been trying to keep the new code as less intrusive as
> possible; re-writing the event handling away from waitNextEvent(old carbon
> not thread safe) isn't something I'd like to deal with at the moment. I
> am open to suggestions of any kind but I am a little bound by the
> framework I'm working with at the moment.
It's not that there's anything wrong with CFSocket per se, it's just that:
o {NS,CF}Stream is usually a better match for TCP code
o {NS,CF}Stream offer features that are hard to replicate using the lower level APIs (various connect-by-name smarts [1], easy TLS integration, and so on)
o If one is using CFSockets just for run loop integration, GCD makes a great replacement.
However, given that your code has no long-term future, it's probably not worth worrying about this too much.
Share and Enjoy
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
[1] Including:
<http://lists.apple.com/archives/ipv6-dev/2011/Jul/msg00009.html>
_______________________________________________
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