Companion app - location duplicates

[Dirk Hohndel]

Aurélien PRALONG <aurelien.pralong at gmail.com> writes:

>> I have noticed that as well - only for me the duplicate jumps 8h into the
> future as I am at GMT
> OK. I've investigated the problem.
>
> For now, we don't have timezone information in the web-service : timestamp
> is split into date and time, and is saved "as is" in the server. So when I
> send a dive, I send it for the current timezone, and when I get them from
> the web-service, I expect them to be at GMT. I can send them as GMT to
> avoid problems, but a cleaner way would be :
> - Send dives as one XML DateTime (no reason to split the timestamp into 2
> fields)
> - The server translates them to it timezone
> - When the server sends back logs, it sends XML DateTime too, with it
> timezone of choice : we then have an absolute time, so no more confusion

I don't think we want to introduce timezones into the mix. Dive times
for us are ALWAYS local time - so they have no timezone.

The problem here seems to be that for the first automatic fix the
companion appears to send TWO dives. One in local time, one in UTC.

/D