eclipse-sailing-analytics/sailing-analytics
1
0 Fork 0
mirror of https://github.com/eclipse-sailing-analytics/sailing-analytics.git synced 2026-10-09 13:50:57 +00:00
Code Activity

Updated smartphone tracking (markdown)

Browse Source
This commit is contained in:
Fredrik Teschke authored and Wiki User committed 2013-07-11 15:10:02 +02:00
1 parent 0e7f03d894
commit a7e9fc124e
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
wiki/smartphone-tracking.md
+1 -1
View File
@@ -8,7 +8,7 @@ Some important decisions and interface specifications for smartphone tracking ar
## Communication Channels
The current plan is to use up to three channels for communicating:
1. **Servlets:** Everything that is not directly related to a specific Race (or rather RaceLog) is handled via POST and GET servlets, where the data should be described as JSON. Examples are: Creating a Race, managing Competitors.
1. **Servlets:** Everything that is not directly related to a specific Race (or rather RaceLog) is handled via POST and GET servlets, where the data should be described as JSON. Examples are: Creating a Race, managing Competitors. Caveats: replication and persistence!
2. **RaceLog:** All the "master data" communication concerning one race in particular should piggyback on the existing RaceLog-mechanism, which already deals with semi-connectedness, persistence and replication. Examples for this are: adding competitors to a race, mapping tracking devices to competitors, starting a race, defining the course layout.