Re: Which API should I use for sockets
Re: Which API should I use for sockets
- Subject: Re: Which API should I use for sockets
- From: Douglas Davidson <email@hidden>
- Date: Fri, 13 Jun 2003 11:45:38 -0700
On Friday, June 13, 2003, at 11:07 AM, Scott Thompson wrote:
In selecting between CFSocket and NSSocketPort... it would depend
largely on which API your more comfortable with and what API is used
throughout the rest of your application. If you are writing an
application to the Carbon API set then CFSocket is going to fit into
your code more naturally. If, in contrast, you are using Cocoa,
NSSocketPort will probably not be out-of-place.
I should point out that NSSocketPort is not a general-purpose socket
API. It is a socket-based subclass of NSPort, which means that it can
be used for networked communications between two Cocoa processes (in
particular via Distributed Objects) but is not suitable for
communicating with non-Cocoa clients.
Douglas Davidson
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.