|client_heart_beat([VALUE])||get/set the client heart-beat|
|server_heart_beat([VALUE])||get/set the server heart-beat|
|last_received()||get the time at which data was last received, i.e. read from the network socket|
|last_sent()||get the time at which data was last sent, i.e. written to the network socket|
|beat([OPTIONS])||send a NOOP frame (using the noop() method) unless the last sent time is recent enough with regard to the client heart-beat settings|
Starting with STOMP 1.1, each end of a STOMP connection can check if the other end is alive via heart-beating.
In order to use heart-beating (which is disabled by default), the client must specify what it wants before sending the CONNECT frame. This can be done using the client_heart_beat and server_heart_beat options of the new() method or, this is equivalent, the client_heart_beat() and server_heart_beat() methods on the Net::STOMP::Client object.
After having received the CONNECTED frame, the client_heart_beat() and server_heart_beat() methods can be used to get the negotiated values.
To prove that it is alive, the client just needs to call the beat() method when convenient.
To check if the server is alive, the client just needs to compare the current time and what is returned by the last_received() and server_heart_beat() methods. For instance:
Lionel Cons <http://cern.ch/lionel.cons>
Copyright (C) CERN 2010-2013
|perl v5.20.3||NET::STOMP::CLIENT::HEARTBEAT (3)||2013-11-28|