Julian Verdurmen comments

Results 414 comments of


                                            Julian Verdurmen

Serialize characters excluded in XML specs

> Looks like there's a rather simple way to de/serialize `string` fields/properties as `CData` or `Base64`-encoded. > I'm considering a `YAXStringEmbeddingAttribute` which allows for `StringEmbedding.None` | `StringEmbedding.CData` | `StringEmbedding.Base64`. Sounds...

Serialize characters excluded in XML specs

> YAXSerializationOptions.StripInvalidXmlChars I like that one :)

Split IYAXSerializer<T> to IYAXSerializer<T> and IYAXDeserializer<T>

@axunonb please your opinion on this

Split IYAXSerializer<T> to IYAXSerializer<T> and IYAXDeserializer<T>

See https://github.com/YAXLib/YAXLib/pull/196

Split IYAXSerializer<T> to IYAXSerializer<T> and IYAXDeserializer<T>

Oops thats a typo, it should be multistage indeed

Split IYAXSerializer<T> to IYAXSerializer<T> and IYAXDeserializer<T>

this isn't planned anymore

Split IYAXSerializer<T> to IYAXSerializer<T> and IYAXDeserializer<T>

I think it needs a case why we need it. Otherwise its YAGNI.

Extend caching and pooling for better performance

Cool stuff. But is there a max cache size? Or what happens if there is a memory shortage?

Extend caching and pooling for better performance

Yes otherwise you could get memory leaks or out of memory issues.

Extend caching and pooling for better performance

Maybe we could do something with https://docs.microsoft.com/en-us/dotnet/core/extensions/caching Or https://github.com/NLog/NLog/blob/dev/src/NLog/Internal/Collections/MruCache.cs (also tests there)