> Le 4 nov. 2018 à 20:01, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Seems like Current time(*) from a client might be cached incorrectly as an > optimization, since Current time and Current time(*) on the server both > returned correct values.
Looks like. But I'm wondering about that "optimisation", given Current time(*) is slower than Current time and seems to send a request to the server. > This completely broke credit card processing I don't like to use local time since I noticed that nightly processes could create records with timestamps prior to records created before (sic), I use timestamps UTC based instead. I'd like to have 4D functions for UTC: <http://forums.4d.com/Post/FR/14715589/1/14715789#14715590> In waiting, see Miyako's nice use of XML DECODE in the same thread. I used it to get zone offset in seconds: <http://forums.4d.com/Post/FR/14701949/1/14701950#14928049> -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
