Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Are the tracks pre-recorded? How likely is it that they'll change? Commented May 13, 2013 at 9:39
  • 2
    How many points are we talking about? Is it quicker to download the raw data (mobile? 3G?) to the device then do the calculations, or is it better to do the calculations server side and just blip down the few bytes that the user will actually see? Commented May 13, 2013 at 13:25
  • @YannisRizos: Very likely. Future version of web app should even allow on-line update of track being recorded as viewers watch it. Commented May 13, 2013 at 18:35
  • @DanPichelman: Points array size may of course vary, but at this stage of app development (design) I assume average track to have between 500 and 5000 points. Commented May 13, 2013 at 18:38
  • "But, right now, after reading some docs and pages, I can see clearly, that I may be wrong." Do you have any actual reference to support this impression? Which docs and which pages? Commented Jul 24, 2013 at 14:45