[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-342) Can we relax the requirement of int64 numbers being represented as strings in the JSON Format for integer numbers that don't lose precision in ECMAScript when represented as numbers?
[ http://tools.oasis-open.org/issues/browse/ODATA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33001#action_33001 ] Stefan Drees commented on ODATA-342: ------------------------------------ That's good news for me. The size argument was a honeypot ;-) I do not understand scenarios anymore, where JSON is sent uncompressed over the wire and size is seen as a problem. When my tools receive JSON over the network, i usally treat all scalar entries as strings to carefully start peeling them off and finally digesting them. So there is allways a transcoding layer between my model in javascript/php whatever and the transport containers content. Is this direct transfer of typed integers an important part of processing the wild openness inside open data content? (This is a real question, sorry for eventually using funny words). > Can we relax the requirement of int64 numbers being represented as strings in the JSON Format for integer numbers that don't lose precision in ECMAScript when represented as numbers? > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ODATA-342 > URL: http://tools.oasis-open.org/issues/browse/ODATA-342 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData JSON Format > Environment: [Proposed] > Reporter: Hubert Heijkers > Priority: Minor > > The current JSON Format specification requires all Int64 numbers to be represented as strings because of the limitation of numbers in JavaScript were these numbers get stored as 64-bit binary format IEEE values and therefore lose precision past 15 digits. However numbers up to that point could still be represented as numbers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]