com.hazelcast.nio

Interface OutboundFrame

All Known Subinterfaces:

TextCommand

All Known Implementing Classes:

AbstractTextCommand, BulkGetCommand, ClientMessage, DeleteCommand, ErrorCommand, GetCommand, HttpCommand, HttpDeleteCommand, HttpGetCommand, HttpHeadCommand, HttpPostCommand, IncrementCommand, NoOpCommand, Packet, SetCommand, SimpleCommand, StatsCommand, TouchCommand, VersionCommand

@PrivateApi
public interface OutboundFrame

Represents something that can be written to a Connection. There are different types of OutboundFrame:

1. Packet: for member to member and old-client to member communication
2. TextMessage: for memcached and rest communication
3. ClientMessage: for the new client to member communication

Till so far, all communication over a single connection, will be of a single Frame-class. E.g. member to member only uses Packets. There is no need for an InboundFrame interface.

See Also:

Data, Connection.write(OutboundFrame)

Method Summary

Modifier and Type	Method and Description
boolean	isUrgent() Checks if this Frame is urgent.

Method Detail

isUrgent

boolean isUrgent()

Checks if this Frame is urgent. Frames that are urgent, have priority above regular frames. This is useful to implement System Operations so that they can be send faster than regular operations; especially when the system is under load you want these operations have precedence.

Returns:

true if urgent, false otherwise.