init patch for redis_logger:template,logging logic might have some space... #361

wants to merge 1 commit into


None yet
1 participant

Since managing the data was critical for debugging in our project,I briefly write a code for showing "redis" activity information from one request.The information should include "what Key was used" or "what was the Value" or "how fast" or "which function used"..etc

1,I really want "expire" information of the key.So might add this feature,which will be available when it was specified to do so( on
2,Templates can be better
3,I couldn't use "inherit class and return new class" sort of logic,as in sql or cache,but "replacing a function" sort of logic as instanced StrictRedis wouldn't be shared on one request.I'm wondering there might be more better way than what I implemented.
4,Calling function information might be acquired in more sophisticated way.

@shootstar shootstar closed this Mar 18, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment