ibis.ipl
Interface SendPortIdentifier

public interface SendPortIdentifier

Identifies a SendPort on the receiver side.

Method Summary

boolean	equals(java.lang.Object other) The equals method is mentioned here just as a reminder that an implementation must probably redefine it, because two objects representing the same SendPortIdentifier must compare equal (and result in the same hashcode).
int	hashCode() The hashCode method is mentioned here just as a reminder that an implementation must probably redefine it, because two objects representing the same SendPortIdentifier must result in the same hashcode (and compare equal).
IbisIdentifier	ibis() Returns the IbisIdentifier of the SendPort corresponding to this identifier.
java.lang.String	name() Returns the name of the SendPort corresponding to this identifier.
java.lang.String	type() Returns the name of the PortType of this identifier.

Method Detail

type

public java.lang.String type()

Returns the name of the PortType of this identifier.

Returns:

the name of the porttype.

name

public java.lang.String name()

Returns the name of the SendPort corresponding to this identifier.

Returns:

the name of the sendport.

ibis

public IbisIdentifier ibis()

Returns the IbisIdentifier of the SendPort corresponding to this identifier.

Returns:

the ibis identifier.

hashCode

public int hashCode()

The hashCode method is mentioned here just as a reminder that an implementation must probably redefine it, because two objects representing the same SendPortIdentifier must result in the same hashcode (and compare equal). To explicitly specify it in the interface does not help, because java.lang.Object already implements it, but, anyway, here it is.

equals

public boolean equals(java.lang.Object other)

The equals method is mentioned here just as a reminder that an implementation must probably redefine it, because two objects representing the same SendPortIdentifier must compare equal (and result in the same hashcode). To explicitly specify it in the interface does not help, because java.lang.Object already implements it, but, anyway, here it is.