[FMP Standards] Best Practices > Host Timestamp fields

[Daniel Smith (Confluence)]

Daniel Smith commented on a page

Re: Host Timestamp fields It was recently pointed out to me by LaRetta that there is no need for using the GetField function in the creationHostTimestamp field's auto-enter calc, just Get ( CurrentHostTimeStamp ) will do the same thing. Reply • Like

Stop watching space • Manage notifications This message was sent by Atlassian Confluence 5.6.6

[Jeremy Bante]

While we're on the topic, what do folks think about host time vs. UTC? For solutions always connected to a host, Get ( CurrentHostTimestamp ) presumably keeps times between machines in better sync with each other. On the other hand, we're seeing more and more solutions with devices that do not maintain an active connection to a host, but sync periodically. Get ( CurrentTimeUTCMilliseconds ) presents an obvious advantage for those applications.

[Arnold Kegebein]

I agree, UTC is the way to go. Also makes sync between offline devices from different timezones easier.

[Matt Petrowsky]

Jeremy, can you post the comment on the page via Disqus? I'd reply here, but most people using filemakerstandards.org say the value they get is from being able to read the interaction.

In short, however, my vote would be utc - way easier and universal.

The question would be 1) suggest it as an additional (optional) field or replace host timestamp. I can see cases where determining timezone programmatically between server - think "home office" and client could be beneficial. Therefore, replacing host timestamp with utc is less preferable to adding another optional field.

--
You received this message because you are subscribed to the Google Groups "FileMaker Development Standards" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fmstandards...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.