Re: Socket and Objective-C
Re: Socket and Objective-C
- Subject: Re: Socket and Objective-C
- From: John Pannell <email@hidden>
- Date: Mon, 10 Sep 2001 15:20:44 -0600
On Monday, September 10, 2001, at 02:51 PM, Dave Fayram wrote:
>
Well, one way is to use the underlying BSD calls to establish the
>
socket and
>
then make an NSFileHandle use the socket. This approach works ok, but
>
not
>
really all that well.
What is it about this that doesn't work well?
I'm getting set to use NSFileHandle to wrap BSD socket calls, based on
previous feedback on dev lists... it seemed like people felt that
CFSocket had some bugs in it, and OmniNetworking (while well written)
was quite large if one didn't need all of its power.
Another option is small sockets
http://smallsockets.sourceforge.net
Yet another option is the EDInternet framework
http://www.mulle-kybernetik.com/software/ALX3000/edinternet.html
The Omni dev list has posts on this topic:
http://www.omnigroup.com/search-bin/macosx-dev?Search=socket
Hope some of this helps - I would enjoy any comments on the
performance/bugginess/difficulty of the various socket options from
people who have used them... specifically
options: OnmiNetworking, smallsockets, CFSocket, NSFileHandle/BSD,
EDInternet
which of these operate asynchronously like NSFileHandle (i.e.
readInBackgroundAndNotify:)?
Does CFSocket really have bugs? If so, what?
Any comments/comparisons between these options?
John Pannell