Re: porting code that uses NSSocketPort

[Morgan Giddings]

I am not at all clear how using an NSFileHandle would help.

I have a DO based, client/server app where there can be up to 20 or  
more distributed processes (servers) on a cluster/grid, each talking  
to the "client" to perform processing and return results.  There is  
extensive interaction (method invocation) between these objects on  
the disparate machines and the client.

Is that really something that can be done with NSFileHandle?

Morgan



On Sep 15, 2005, at 4:02 AM, Richard Frith-Macdonald wrote:

> On 2005-09-15 04:27:42 +0100 Morgan Giddings <giddings@unc.edu> wrote:
>
>
> > Hi
> > I have a command-line app I am trying to port from Mac OS X to   
> > GNUStep.  It makes extensive use of NSSocketPort.  I'm running  
> > into  troubles, because it appears that the class interface  
> > definition for  NSPort under GNUStep is different than in Cocoa.
>
> Yes ... it says in the documentation ... 'Note that this class is  
> incompatible with the latest OS X version.'
>
> That's because the GNUstep class is a lot older than the MacOS-X  
> class, and implements the behavior of OpenStep/NeXTstep ports  
> (which simulate the behavior of Mach ports).
>
> You are probably better off using NSFileHandle.