You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sirona.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2015/11/10 23:52:09 UTC
bug in path tracking regarding time?
Hi guys (again ;)),
is it expected to use system.nanotime
in org.apache.sirona.pathtracking.PathTrackingInformation#PathTrackingInformation
and compare it to Date#getTime in the datastore?
nanotime is not expected to be date related and seems it is really
different on some systems.
Not sure the best resolution for this one:
- currentTimeMs will be quite not precise enough
- nanoTime doesnt allow a good querying
wdyt?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
Re: bug in path tracking regarding time?
Posted by Olivier Lamy <ol...@apache.org>.
Thanks for fixing that!!
On 12 November 2015 at 09:25, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> fixed computing an offset using currentTimeMs and nanoTime. can be few ms
> wrong strictly speaking but should be enough for us.
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2015-11-10 14:52 GMT-08:00 Romain Manni-Bucau <rm...@gmail.com>:
>
> > Hi guys (again ;)),
> >
> > is it expected to use system.nanotime
> > in
> org.apache.sirona.pathtracking.PathTrackingInformation#PathTrackingInformation
> > and compare it to Date#getTime in the datastore?
> >
> > nanotime is not expected to be date related and seems it is really
> > different on some systems.
> >
> > Not sure the best resolution for this one:
> > - currentTimeMs will be quite not precise enough
> > - nanoTime doesnt allow a good querying
> >
> > wdyt?
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > <http://rmannibucau.wordpress.com> | Github
> > <https://github.com/rmannibucau> | LinkedIn
> > <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com>
> >
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: bug in path tracking regarding time?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
fixed computing an offset using currentTimeMs and nanoTime. can be few ms
wrong strictly speaking but should be enough for us.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>
2015-11-10 14:52 GMT-08:00 Romain Manni-Bucau <rm...@gmail.com>:
> Hi guys (again ;)),
>
> is it expected to use system.nanotime
> in org.apache.sirona.pathtracking.PathTrackingInformation#PathTrackingInformation
> and compare it to Date#getTime in the datastore?
>
> nanotime is not expected to be date related and seems it is really
> different on some systems.
>
> Not sure the best resolution for this one:
> - currentTimeMs will be quite not precise enough
> - nanoTime doesnt allow a good querying
>
> wdyt?
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>