user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
* lei timestamp resolution for mail synchronization
@ 2021-05-07  0:13 Eric Wong
  0 siblings, 0 replies; only message in thread
From: Eric Wong @ 2021-05-07  0:13 UTC (permalink / raw)
  To: meta

Is millisecond resolution "good enough" for mail synchronization?

Or maybe even seconds is sufficient...

When syncing mail across machines/devices/reboots, using the
system clock seems required (anybody syncing mail also uses
NTP, right?).

While Time::HiRes allows access to .tv_nsec for some APIs;
Time::HiRes::stat converts it to a double-precision float
(NV/Numeric Value in perlguts-speak).  That's not enough for
microsecond accuracy, even; and of course I don't think most
kernels or HW is actually accurate down to the nanosecond level.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-05-07  0:13 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-07  0:13 lei timestamp resolution for mail synchronization Eric Wong

user/dev discussion of public-inbox itself

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 meta meta/ \
	public-inbox-index meta

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for project(s) associated with this inbox:

AGPL code for this site: git clone