Actual Pipelining, not Batch Processing, in PHP+Redis -

there's lot of information on "pipelining" in php+redis on web. however, when start looking @ examples, not single 1 of them actual pipelining. batch processing. examples, let's take predis ->pipeline() (https://github.com/nrk/predis) , phpredis ->multi() (https://github.com/nicolasff/phpredis). suspend execution of commands , instead collect commands buffer, execute them batch when calling ->execute() / ->exec() later.

disadvantages: - has allocate command buffer can grow large many commands - needs round-trip server once every batch of commands

the behaviour expect pipelining mode is: start sending commands pass them client, not buffer them. return before response command has arrived. allow send more , more commands while previous ones "in flight". once in while, collect responses client have arrived, without waiting responses have not yet arrived.

the strange thing examples pass constants client called "pipelining", yet describe behaviour batch processing.

big question: how can put clients pipelining mode?