mirror of
https://github.com/predis/predis.git
synced 2026-08-24 20:39:42 +00:00
Daniele Alessandri
1b9e10bdd8
Connection classes should just handle, convert and return simple Redis types while parsing and transforming structured replies should be done by consumers (see Predis\Client or Predis\Transaction\MultiExecContext). This actually makes more sense considering that parsing a complex response with the associated command parser may require different actions. As an example, the result of EXEC is a multibulk that holds the actual responses, so we really need to parse each one of its elements and we should also make sure that iterable multibulks are consumed. We already did that previously, but it was weird knowing that command parsers were applied by the connection class. This also moves some duplicated logic away from each connection class implementation which is a nice bonus.