Hi Justin, in this case, use low-level routines for the communication (receive BLOB for example or some equivalent using Keisukes cUrl Plugin) and parse the received data „by hand“. Tedious, but you have full control.
> Am 03.11.2017 um 00:12 schrieb Justin Leavens via 4D_Tech > <4d_tech@lists.4d.com>: > > Keisuke Miyako wrote >> it seems correct that a number is mapped to real, according to JSON >> specification >> ... >> >> if you must exchange Int64, I think it is the responsibility of the sender >> to use string. >> >>> 2017/11/03 3:56、Justin Leavens via 4D_Tech < > >> 4d_tech@.4d > >>> のメール： >>> Unfortunately, 4D seems to munge the value immediately within the object >>> when the HTTP response is returned in an object. > > I'm sure you are correct. Unfortunately, I don't have the power to force a > change from the provider. > > > > -- > Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
