Re: porting code that uses NSSocketPort
Richard Frith-Macdonald <[email protected]>
| Newsgroups | gmane.comp.lib.gnustep.user |
|---|---|
| Message-ID | <2a50d2ff62af11d6d3b6c5ef7df6f910@blackbox> |
On 2005-09-15 13:08:13 +0100 Morgan Giddings <[email protected]> wrote: > 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? Sorry, I was under the impression that you were using NSSocketPort to send directly rather than using NSConnections. No, NSFileHandle is not good for DO. I'm used to DO processes using named ports ... in which case there is generally no need to work with specific TCP/IP port numbers. However, if you do need to use specific port numbers for DO communications, then portWithNumber:onHost:forceAddress:listener: is the method to use, and you can easily implement the equivalent new MacOS-X method in a category if you like.