On Mon, Jan 26, 2015 at 5:26 PM, Rudolf J Streif <[email protected]> wrote: > It probably won't be my last question about AMB as I am digging through it. > Thank you for your patience, Kevron. >
Happy to help. > Different data sources can potentially provide the same VehicleProperty, for > instance VehicleProperty::VehicleSpeed could be provided by GPS, CAN, OBD > (well, it is not provided by the gpsnmea plugin as it defines a property > GPSSPEED). > That's a good point. GpsSpeed may have existed before AMB had multiple-provider/property support. It think it would make sense for GPS to also provide VehicleSpeed. > What happens if there are multiple data sources for the same property? AMB > just passes it on to the subscribers regardless? Each source should have a unique id. When you subscribe from a sink, you can use the overloaded subscribe call[1] to filter by the source you want. If you don't use this overload, the behavior is that all providers of that property will be passed. You can also get a list of sources for a given property with the sourcesForProperty() call[3]. > Is there a way to subscribe > to a property from a specific provider (not that I need it, just asking)? Is > there a way to tell what plugin provided the property (don't need it either, > just wrapping my head around it)? > AbstractPropertyType has a sourceUuid member[2] the tells you which source produced the property. The DBus sink plugin takes advantage and creates DBus objects per property, per source. It also has methods to get an interface object by zone or source. [1] - http://otcshare.github.io/automotive-message-broker/0.13/amb/html/classAbstractRoutingEngine.html#aae6c5d27dc01b4773b6bf77331f86e9f [2] - http://otcshare.github.io/automotive-message-broker/0.13/amb/html/classAbstractPropertyType.html#abe2de53722d28e8e7c2a715b97e1ae48 [3] - http://otcshare.github.io/automotive-message-broker/0.13/amb/html/classAbstractRoutingEngine.html#aef8ad3a6c8d00d7fe9fdb378acf918c0 -Kevron > Thanks, > Rudi > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
