784285 - [WebSMS] Store device timestamp instead of SMSC timestamp for received SMS

Status: RESOLVED WONTFIX

(Core :: DOM: Device Interfaces, defect)

Description

[Fernando Jiménez Moreno [:ferjm]]

As requested in https://github.com/mozilla-b2g/gaia/issues/3087, we need to store the device timestamp instead of the SMSC timestamp when receiving an SMS.

Comment 1

[Fernando Jiménez Moreno [:ferjm]]

https://github.com/mozilla-b2g/gaia/issues/3087 has the 'blocking-basecamp' flag set, so I am asking for blocking-basecamp? here too.

Comment 2

[Vicamo Yang [:vicamo][:vyang]]

That's nonsense.

Comment 3

[Mounir Lamouri (:mounir)]

(In reply to Vicamo Yang [:vicamo][:vyang] from comment #2)
> That's nonsense.

I think it would be appropriate to give a rational here. Saying that a request is "nonsense" without any other explanation is pretty disrespectful IMO.

Comment 4

[Mounir Lamouri (:mounir)]

Re-asking for blocking as Fernando initially did.

Comment 5

[Philipp von Weitershausen [:philikon]]

Vicamo and I talked this over. There's no real advantage to using the SMSC timestamp over the device timestamp, really. If the device's system clock is changed dramatically, messages order is going to be out of whack one way or the other, so that's not a case we should optimize for. We should, however, make sure that clock drift won't cause this to happen. This is a real possibility since SMS messages could easily be just a dozen or so seconds apart, even when typed manually.

I think we should therefore make things symmetric and use the device's timestamp every time.

Comment 6

[Andrew Overholt [:overholt]]

Josh, we'd love UX's input here.  Thanks.

Comment 7

[Fernando Campo (:fcampo)]

I think that there's a little confusion on this topic when comparing this thread with the github equivalent https://github.com/mozilla-b2g/gaia/issues/3087, where it seems that the favourite flavour is to use the server's time.

I'm posting the same message I wrote in there: 
"My understanding is that the final agreement is to leave it as it is, and keep using the server's time to avoid the time drifting situation explained by @vicamo, and let the user deal with their mess if they decide to change device's time . Am I right? If so, the issue could be closed, and if not, we should get an agreement on how we want to solve it in gaia."

I think we should clarify this for once and all, and try to unify points of view and finally take a decision, cause this issue is taking a lot of time. I don't mind long discussions in general, but this specific one looks more like a misunderstanding than opposite sides of a problem

Comment 8

[Philipp von Weitershausen [:philikon]]

Agreed. Let's stick with SMSC.