trying to improve performance for case when blitz of requests flow out. Assume incoming data from socket to be handled is long - say several K after several of requests were pushed out. Observatory shows huge amounts of work in the lists in handleData, plus it is recursive. The approach taken was: for large list L use from front what is needed and return unused data. The issue is every response requires copy of entire data list unnecessarily.
more tests working
added check in bulk to only recurse of not done
fixed call to _makeRedisConsumer to use the data, not the index
removed debug prints
Moved handlers out of RedisConnection into RedisStreamTransformerHandler - allowing testing of the transforms without mocking.
Fixed isInstanceOf expect statement in test ("should properly handle consecutive MultiBulkReplys in single packet")
Removed data_consumers.dart as same functionality in the _RedisConnection implementation
Added benchmark_harness to pubspec
moved transformation code into redis_protocol_transformer.dart library
added publish script to demonstrate the issue
removed no longer used fields in _RedisConnection
cleaned up the publish example and added timing to it. Seems this is not the best case for benchmarking as it requires long running work to demonstrate the issue which is a different use case than benchmark handles.
replies did not ever get cleaned up. Put them in a queue and remove as they fulfilled.
Merge pull request #55 from patefacio/master

Improve performance of stream transformer from List<int> to List<RedisReply>