Memcached2
Memcached2 copied to clipboard
enyim
multi framework targeting
Since many projects have not yet moved to netstandard2.1, it is desirable to make this library a bit more friendly to those projects, leaving them an easy way to move forward
most of the changes are conditional and should not affect the netstandard2.1 implementation.
rewrote the AsyncSocket buffers for NETSTANDARD2_0 || NET471 || NET472 || NET48, all client tests are passing now.
@enyim A kind reminder... I don't want to spin off another NuGet just for the sake of backwards compatibility
@EugeneKrapivin @enyim Can you let me know if there is anything blocking this? This seems very useful to those of us that can't yet move to .net Standard 2.1.
This package seems to have been long deserted unfortunately.
On Fri, Jan 7, 2022, 02:04 David W. Gray @.***> wrote:
@EugeneKrapivin https://github.com/EugeneKrapivin @enyim https://github.com/enyim Can you let me know if there is anything blocking this? This seems very useful to those of us that can't yet move to .net Standard 2.1.
— Reply to this email directly, view it on GitHub https://github.com/enyim/Memcached2/pull/8#issuecomment-1007029421, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6V3NLWDYCXWKAZLVUJPD3UUYUYJANCNFSM42H3RKSA . You are receiving this because you were mentioned.Message ID: @.***>
Thanks @EugeneKrapivin - That's a bummer. Do you have a recommendation for an alternate C# library to interact with Memcached?
@dwgray if you are looking for a supported library then unfortunately it looks that you are out of luck in case of Memcache. You could get this code and build/publish an internal nuget and use it if you want.
I've also used a nuget from https://github.com/vieapps/Enyim.Caching However, it also has some poor support.
Could you consider using a more popular solution like Redis? StackExchange has a great library supported by a huge community.
@EugeneKrapivin what you think about this: https://www.nuget.org/packages/EnyimMemcachedCore/2.5.7
@DenisDoroshko hey, I'm not longer pursuing the matter :) but thanks for the reference. I'll keep it in mind next time I'll need to work with memcache