tick handling and shutdown behaviour

[bashilbers]

Hi guys/girls,

2 questions:

1. Why don't you register a tick handler? I see the declare construct being used, what purpose does it have without having a registered tick handler?
2. Shutdown behaviour. Currently the consumer's invoke method is blocking the shutdown mechanism. I.e. if consuming a particular message takes 3h to consume, and you send in a SIGINT or SIGTERM signal (also, the default supervisord stopping signal), you'll have to wait 3hours until the consumer notices that it should've stopped. Not ideal if you ask me.

[GDmac]

Declare tick should not be used at all, many places it is suggested to use pcntl_signal_dispatch instead.
Inside the drivers, instead of usleep(), could use time_nanosleep, which is interruptable.

pcntl_signal_dispatch();
$nano = time_nanosleep(0, 100000000);
if ($nano === true) {
  // slept
} elseif ($nano === false) {
  // nanosleep fail
  usleep(100000);
} elseif (is_array($nano)) {
  // Interrupted by a signal
  pcntl_signal_dispatch();
  return array(null, null);
}
pcntl_signal_dispatch();

(edit: via GeniusesOfSymfony/WebSocketBundle#125 )