Page History

...

Next Meeting - VHAL / Vehicle Data APIs weekly call - Tuesday 2 9 June - 17:00-18:00 CET

...

Expand

Backlog

Android Compatibility Definition Document
Software architectural task force : Vehicle Data architecture for Android
Comparison of how vehicle properties are managed by Android 9 and 10 (Q) - further inputs
question to address in the group: what do participating companies intend to do with the JAPI (Java API similar to CommonAPI for Android) ? this building block is currently missing
Signal to service translation
Secure access control in Some/IP

Participants

Agenda

Minutes

sync with CCS project

outcome of the sync meeting with Ulf from the CCS project
Stephan: we could change the VSS database for SQLite and request for the properties on demand
Gunnar: there are 3 cases that can be considered
TODO to write prepare a block diagram describing the various cases
Alex :agrees with the 3 cases
Alex: do we really need a database which might be seen as an overkill for me ? some hash-map in memory might be enough
Alex: when the data are not changed at all, what do we do ?
Gunnar: do we need a database ? no, but there is an implementation that exists
Alex: are the feeder and the grapql in the same process ?
Gunnar: I think there are separate processes and we need IPC soemwhere unless we put everything in one process
Stefan: but even if we use one processor we need some thread sync.
Piotr: IMHO using hashmap and sync implementation would result in the same complerxity than using SQLite
Gunnar agreed
Gunnar: debouncing ?
Gunnar: there might be some higher performance database, but basically we need only a key value store

VSS to Franca

...

Page tree