Quote Originally Posted by DEXWERX View Post
The way Javascript and PHP deals with overly large integers - is to export them as a JSON strings.
I remember this being a fiasco when facebook went to 64bit IDs, and broke a bunch of APIs.
Yep, and that raises the question, which toolset (or language) did produce the JSON-serialization
(containing that large Integer-Value in mjk1165's example)...
Apparently it expects a JSON-parser (on the other end), which is capable to understand
(and not mangle) that Integer-Value.

Quote Originally Posted by DEXWERX View Post
The best thing about this class - is it's open source. We can modify it to suit specific needs, and edge case behavior.
Well, I hope mjk1165 is capable of doing that...

As it is currently, I hope he understood from what was said, that he has to use a specific non-default-setting on diles JSON-Bag,
to not run into issues with that Integer (e.g. on a potential back-posting roundtrip with "re-serialized" content to the ServerSide).

The "automatic-fallback-mode to Decimal" I was suggesting (when Integer-Numbers get too large) would hurt nobody
(even in the Default-Setting "Parse-Numbers-into-Doubles") and would require the least efforts, when dile does it himself.

But as said, it was only a well-meant suggestion (take it or leave it)...

Olaf