In computer science's object-oriented programming, a protocol (Java: interface) is what or how unrelated objects use to communicate with each other. These are definitions of methods and values which the objects agree upon in order to cooperate.
For example, in Java (where protocols are termed interfaces), there is the Comparable interface specifies a method compareTo() which implementing classes should implement. So, this means that a separate sorting method, for example, can sort any object which implements the Comparable interface, without having to know anything about the inner nature of the class (except that two of these objects can be compared by means of compareTo()).
The protocol is a description of:
- the messages that are understood by the object,
- the arguments that these messages may be supplied with, and
- the types of results that these messages return.
- the invariants that are preserved despite modifications to the state of the object
- the exceptional situations that will be required to be handled by clients to the object
If the objects are fully encapsulated then the protocol will describe the only way in which objects may be accessed by other objects.
Programming languages that support protocols: Objective-C, Java, C#, D
Note that functional programming and distributed programming languages have a concept which is also called protocol, but whose meaning is subtly different (i.e. a specification of allowed exchanges of messages, emphasis on exchanges, not on messages). This difference is due to somewhat different assumptions of functional programming and object-oriented programming paradigms. In particular, the following are also considered as part of a protocol in these languages:
- The allowed sequences of messages
- Restrictions placed on either participant in the communication
- Expected effects that will occur as the message is handled
See also: class, encapsulation, public interface , private interface