The letter sleeve is just a wrapper around redis, so any data solutions really apply equally to any redis manual. http://redis.io will be the starting point. As for the API, the only things to highlight are:
- most operations are asynchronous and displayed through the Task api; this allows the use of a number of usage patterns, including (but not limited to) the new keywords "async" / "wait"
- operations are separated by data type, therefore .Strings, .Hash, etc.
- the connection is a thread-safe multiplexer and is designed for simultaneous use by several callers - you do not need (and should not) use the connection zone for each subscriber
I am wondering what things you would like to include in more detailed documentation. What would be helpful? What's not clear? What you need?
If you can describe what you need, I can write it: p