Feature/redis module client side caching

[kopffarben]

PR Details

Exeption Handeling and ClientSideCaching

Description

[RedisModuleClientSideCaching] Update to StackExchange.Redis 2.7.4 https://stackexchange.github.io/StackExchange.Redis/ReleaseNotes#274 Enables the complete conversion to ClientSideCaching This is how we get rid of the Custom IsChanged implementation.

All critical methods in the RedisCommandQueue and SubscriberExtension implement the NodeContext and IVLRuntime.Current, so that PersistentMessage can also be promoted to VL from Observables that run concurrently.

Add HelpPatch for "HowTo External Write to Global Channel.vl"

TODO: Implement SerializerEnum(MsgPack, JSon, None) in RedisClient/RedisModule, in Binding "Default, MsgPack, JSon, None" and in Publish and Subscribe. This will be done when VL.MessagePack is ready.

Types of changes

• [x] Docs change / refactoring / dependency upgrade
• [x] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

[azeno]

Thanks! Will have a look at it today. In the meantime: Redis has two modes for caching, what was the reasoning for choosing the second one (broadcasting)? Can we peek into your thought process here a little bit?

Then we were also wondering how the caching modes play together with the transactional reading of the keys. If we only read those for which we got an invalidation message then we might run into inconsistent states, no?

[azeno]

Using the Reference Global Channel help patch, changing the Init mode of "MyInteger" to None or Local does not behave like expected:

First frame:

Fourth frame:

Shouldn't it stick to zero? Is this a misconception on my part?

Here seems to be a typo: There should be a Z instead of S

[azeno]

I'll merge this PR now and create separate issues for the things I mentioned here.