Hi Tom, [snip] > Finally - could you explain the concurrency model in AMB - I'd like to > understand the threading model better, specifically around having multiple > clients delivering inbound events at various frequencies, normalising these > to a standard interface and then potentially delivering these to various > consumers... >
AMB works today in a largely first-in, first-out single-threaded model. As the source produces data it is delivered to applications with a few qualifications: First, data produced at a rate higher than the configured throttling threshold may be filtered. Second, only data for which there is an interested listener will be sent across DBus. There are a few exceptions to the single-threaded first-in, first-out model in a couple of the example plugins. The OBD-II plugin reads and processes data in a separate thread. The OpenCV plugin also does concurrent processing. The CAN generator/simulator plugins also process CAN data in a separate thread. In each of those cases, the plugins, once done with the data, queue the data back into the main AMB thread. This may raise more questions than it answers. -Kevron _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
