Adds XML header docs indicating usage of options on NuCacheSerializerType #19555
+15
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites
Relates to #19544
Description
We currently offer a legacy configuration option for cache serialization that's no longer supported since the introduction of the hybrid cache implementation, and has some issues with particular property types such as integers.
To make it work changes would be needed to property type converters, e.g.
I considered that as there's no reason to use this option over the faster and more compact
MessagePack
, we would obsolete the options and schedules the removal in 17.However we have some integration tests that rely on it for assertions. Possibly we could make those work with
MessagePack
, but it didn't seem straightforward. Also this got me thinking that the one benefit of this option is that it's more readable, so given that it's worth keeping around for these tests (and potentially others in future).As such I've limited changes to just providing more information on appropriate usage.