From: <si...@mu...> - 2013-10-30 19:13:16
|
> - Do we want to store all laps or only best laps? Do we want to store both > but handle best laps in a different way (see replay suggestion)? That's actually a difficult decision. I would suggest a unified approach with replay to store 'results-XXXXXXX.xml' (ie. laptimes) with setups. As the car will be lighter with less fuel, the 'Hall of Flame' lap will be somewhat difficult to determine. Do 'we' just say fastest ever for Driver 'Z' in Car 'X' on Track 'Y' in Practice/Race mode? Do 'we' only consider the human drivers? How do we consider multiple humans in a split-screen race? It would fun to be able to see lap times for all (say) 20 laps of a practice, and see the hot/cold laps building to the best time. > - For the "registration" I was thinking, as a start point, on making it > somewhat simpler than a full registration with email on the webserver (I > personally find those thing really annoying). > I was thinking on SD getting assigned an unique ID on first connection to > the web server, this id get stored on a config file on the PC and used to > track the user (I know this method is not as secure as a full > registration...) As a suggestion don't worry about getting all this implemented in the menu system just yet, as the menus will probably be moved to a different code base - just do the 'submit' button. The settings can be stored in the configuration XML files without needing to expose them to the user. As a dev you can hand edit files to set values. A pseudo-random token might be sufficient. Each time a new user (or one without a token) submits you just give them the next in the 'list', by the fact that it's random means it's hard to guess to fake a user. Rather than pre-generating a list of random numbers, you can AES128 encrypt a numeric-count with a secret to get an automatic/non-repeating 'list' of 'random' tokens. I can send you a snippet of python to do this is if you are interested. Simon |