Re: NSSocketPort == BSD Socket

2008-12-05 Thread Douglas Davidson
On Dec 5, 2008, at 10:21 AM, Kirk Kerekes wrote: My core point (which seems to have gotten lost in this thread) is that the Apple docs _used_ to assert that NSSocketPort was useless for anything except DO. 1. This _may_ not ever have been true. Just from looking at the API, it is patent

Re: NSSocketPort == BSD Socket

2008-12-05 Thread Kirk Kerekes
Well it looks like you ought to be able to use NSPortMessage's sendBeforeDate: method, if you are seeking a pure NSPort-and-friends technique, but I've never tried that. It actually looks like it might be handy, if it works. It would handle some of the overhead tasks that otherwise one must

Re: NSSocketPort == BSD Socket

2008-12-04 Thread Michael Ash
On Thu, Dec 4, 2008 at 7:52 PM, Kirk Kerekes <[EMAIL PROTECTED]> wrote: > -[NSSocketPort socket] returns a file descriptor. Write to it. > > Init an NSFileHandle with it. (-[NSFileHandle initWithFileDescriptor:]) > > > It's all just sockets/files/descriptors. Well, you're not using NSSocketPort to

Re: NSSocketPort == BSD Socket

2008-12-04 Thread Kirk Kerekes
-[NSSocketPort socket] returns a file descriptor. Write to it. Init an NSFileHandle with it. (-[NSFileHandle initWithFileDescriptor:]) It's all just sockets/files/descriptors. But "raw messaging" is not the same as writing raw bytes to a TCP stream. All that means is that you can use the s