An NSPort​Message defines a low-level, operating system-independent type for inter-application (and inter-thread) messages. Port messages are used primarily by the distributed objects system. You should implement inter-application communication using distributed objects whenever possible and use NSPort​Message only when necessary.


An NSPort​Message object has three major parts: the send and receive ports, which are NSPort object that link the sender of the message to the receiver, and the components, which form the body of the message. The components are held as an NSArray object containing NSData and NSPort objects. NSPort​Message's send​Before​Date:​ message sends the components out through the send port; any replies to the message arrive on the receive port. See the NSPort class specification for information on handling incoming messages.

An NSPort​Message instance can be initialized with a pair of NSPort objects and an array of components. A port message's body can contain only NSPort objects or NSData objects. In the distributed objects system the byte/character arrays are usually encoded NSInvocation objects that are being forwarded from a proxy to the corresponding real object.

An NSPort​Message object also maintains a message identifier, which can be used to indicate the class of a message, such as an Objective-C method invocation, a connection request, an error, and so on. Use the msgid and msgid methods to access the identifier.


Creating Instances

- init​With​Send​Port:​​receive​Port:​​components:​​

Initializes a newly allocated NSPort​Message object to send given data on a given port and to receiver replies on another given port.

Sending the Message

- send​Before​Date:​​

Attempts to send the message before a​Date, returning YES if successful or NO if the operation times out.

Getting the Components


Returns the data components of the receiver.

Getting the Ports


For an outgoing message, returns the port on which replies to the receiver will arrive. For an incoming message, returns the port the receiver did arrive on.


For an outgoing message, returns the port the receiver will send itself through. For an incoming message, returns the port replies to the receiver should be sent through.

Accessing the Message ID


Returns the identifier for the receiver.


Inherits From