Pretty much all JVM-based timestamp mechanisms measure time as milliseconds since the epoch – so no, nothing standard** that will give seconds since epoch. Your function can be slightly simplified as: (quot (System/currentTimeMillis) 1000) ** Joda might have something like this, but pulling in a third-party library for this seems like overkill.
I strongly advise you to use Moment Date lib when working with dates in js. It’s really light and awesome. var timeStamp = ( moment(‘2009-07-15 00:00:00’).unix() )*1000
I wrote a custom deserializer to handle timestamps in seconds (Groovy syntax). class UnixTimestampDeserializer extends JsonDeserializer<DateTime> { Logger logger = LoggerFactory.getLogger(UnixTimestampDeserializer.class) @Override DateTime deserialize(JsonParser jp, DeserializationContext ctxt) throws IOException, JsonProcessingException { String timestamp = jp.getText().trim() try { return new DateTime(Long.valueOf(timestamp + ‘000’)) } catch (NumberFormatException e) { logger.warn(‘Unable to deserialize timestamp: ‘ + timestamp, e) …
The timestamp is used for allowing the server to optimize their storage of nonces. Basically, consider the read nonce to be the combination of the timestamp and random string. But by having a separate timestamp component, the server can implement a time-based restriction using a short window (say, 15 minutes) and limit the amount of …
Use Time.at. Time.at(1335437221) # => 2012-04-26 12:47:01 +0200
Unix Time is usually a 32-bit number of whole seconds from the first moment of 1970 in UTC, the epoch being 1 January 1970 00:00:00 UTC. That means a range of about 136 years with about half on either side of the epoch. Negative numbers are earlier, zero is the epoch, and positive are later. …
A unix time stamp is defined as the number of seconds since January 1, 1970 UTC, except not counting all the seconds. This is somewhat ridiculous and one has to wonder what the point of it is, so I agree that this is a silly question. Anyway, lets look at some platform documentation for time_t …
You can initialise a Date object and call getTime() to get it in unix form. It comes out in milliseconds so you’ll need to divide by 1000 to get it in seconds. (new Date(“2013/09/05 15:34:00”).getTime()/1000) It may have decimal bits so wrapping it in Math.round would clean that. Math.round(new Date(“2013/09/05 15:34:00”).getTime()/1000)
If you get this error and you’re not using an obviously wrong timestamp, check your units. fromtimestamp expects a timestamp in seconds, whereas it’s quite common to get timetstamps in milliseconds (e.g. I found this when trying to parse a timestamp produced from Moment.js in a calendar widget). Take the timestamp 1523443804214 – it’s 11th …