Wow - great work getting this far! On another project I maintain, I'm also switching over to StackExchange.Redis. I'm maintaining a PR that has all of the things necessary to do so. Here's the list we'll need to get this fully implemented:
[x] Use NetDataContractSerializer as default serialzier, but allow it to be customizable.
[ ] Support .NET 4.0 and 4.5 releases.
[x] Bring over parts of ServiceStack.Redis to support distributed locking?
[x] Update README with changes & contributors.
So, what I'm going to do is create a separate branch, stackexchange-redis, to maintain these changes. I'm going to pull in your code and do some fix-ups (like keeping some of the naming conventions of private variables etc.) Then I'm going to re-work some of it so that the build process will support .NET 4 and 4.5. I'm also going to have to add some references back to the ServiceStack.Redis project since we'll most likely have borrowed some code (distributed locking etc).
Thanks again - I really appreciate all of the leg work you did on this one!
Wow - great work getting this far! On another project I maintain, I'm also switching over to StackExchange.Redis. I'm maintaining a PR that has all of the things necessary to do so. Here's the list we'll need to get this fully implemented:
NetDataContractSerializer
as default serialzier, but allow it to be customizable.So, what I'm going to do is create a separate branch,
stackexchange-redis
, to maintain these changes. I'm going to pull in your code and do some fix-ups (like keeping some of the naming conventions of private variables etc.) Then I'm going to re-work some of it so that the build process will support .NET 4 and 4.5. I'm also going to have to add some references back to the ServiceStack.Redis project since we'll most likely have borrowed some code (distributed locking etc).Thanks again - I really appreciate all of the leg work you did on this one!