I have no experience with the JDO stuff, so I can't comment on it.
On Sat, Apr 11, 2009 at 5:33 AM, Dean S. Jones <[email protected]> wrote: > > Every time I run into this kind of issue, BitSet, BigInteger, > BigDouble.... I dig into the source code and find one common element: > long, long, long. > How big exactly are the numbers that you are dealing with in your data entry fields that they don't fit into a regular integer (+/- about 2 billion). And the long use in BigInteger & BigDouble would be strictly for performance reasons. You should be able to (carefully) replace them with ints & it'll still work, albeit more slowly for bigger numbers. > > > 3 GWT projects I thought I was smarter than the GWT team and > implemented the emul classes and serializers. Worked most of the time, > but failed on the edge cases. There's plenty of stuff out there about how to emulate big integers (it really isn't that difficult to do - but difficult to get right with good performance). > When you work at a Bank and your numbers > go wrong, and the skew is in the Billions, well, you fall back to > strings and do the math on the server. Yes - that is the correct approach that should be taken when dealing with important data - let the server deal with parsing it. > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
