
Post by
jpafonso | 2017-10-26 | 12:28:30
I'm not understanding what you are saying with de-synchronism between client and server, so maybe I misunderstood what you were discussing first. Probably, I'm missing how you are doing it.
My guess was, you prepare a page for each request with all the data of the moment, and it is the job of the client to draw the winds at least. Doesn't make sense in this case to ask the winds (on mouseover events) to the server with an ajax like request because it would strain it, and "all" the winds should have been sent in each request anyway, to be drawn. So there shouldn't be any contradiction in the winds design and what the mouse indicates: if I go with the mouse around an anticyclone, I must witness all kind of angles, 0º for winds from the north, 180º from north, etc... but at least one time, it was not what happened. Instead, I found those angles on another position where the winds was drawn more or less constant. My impression was, the numerical data was right with what virtual regatta was showing (and so, the routes suggested, I guess), but the winds drawing was shifted... at least that time.
PS.: I finish turning at Porto Santo, an hour ago... the 10 minute cycle you were saying was not the source of many crashes against land in the past? When we thought we were curving just in time, but the VR server would put our turning point much more forward? :-)