I am not sure if I understand what you are trying to achieve here with the FTP server.
EDIT------------Actually there is an Export/import function in RCS. Why did we use it? ------------------------------------------------------------
I think the best and simplest bet is to enable two functions: 1) export the car settings into a file; 2) import the car setting from a file. Basically, similar to export/import function of the Tyre profile. We can distribute the car setting file off-line via email for instance. No need to have a centralised DB online. This is a nightmare especially with managing name conflicts, overwrites, ect. You do not want go there. K.I.S.S. principle. I would also suggest the same for the event settings.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Once the two functions are implemented, the you can also add an online option where the file can saved or retrieved from an online shared repository.
Instead, one thing that would be nice to have synchronised through the server would be the weather patterns. This would allow us to make full use of RCS's features even in an online event. I do not how you have implemented the weather changing pattern in the code but the simplest solution here would be to load the pattern from a file. Again, an export/import pair of functions could do. For instance, Marcel could use his instance to generate and export a weather pattern file for a two hour race (actually could be 3 files for practice, qualify and race. Or one single file for an event consisting of practice, qualify and race). Then he would send the file to us via email and we would load the pattern on our RCS instances before the event. Alternatively, Marcel could load the file on the server and then the other instances could use it for generate the local weather patterns.