Why jsonSerialization config value must be divisible by 1024?

Asked Sep 22 '16 at 07:52

Active Sep 23 '16 at 01:02

Viewed 72 times

I was searching how to update the maximum json serialization size in web.config, and I have found this famous post: Can I set an unlimited length for maxJsonLength in web.config?

What I would like to ask is, under the accepted answer, there are comments about the maximum size: 2147483647 vs 2147483644

And one of the comments said they are practically the same because 2147483644 is the maximum integer divisible by 1024 in range.

Does that mean, jsonSerialization attribute value must always be divisible 1024? For example if I set it to 1025, 1026...2047, is it the same as setting it to 1024? And why is it so?

edited May 23 '17 at 11:51

Community

asked Sep 22 '16 at 07:52

shole

4,046
2
29
69

I'd guess its something to do with byte allocation in memory. – Ashley Medway Sep 22 '16 at 08:00
@AshleyMedway I think so, but I can't find any documents supporting this, I do not even know is the claim in that comment is true... – shole Sep 22 '16 at 08:33

Why jsonSerialization config value must be divisible by 1024?

0 Answers0