Hello Tom, > While groking AMB, I happened across the murphyplugin. > Therein, I see some indication of traffic from murphy to AMB; > "Received a message from Murphy" > "recvfrom_msg(mrp_transport_t *transp, mrp_msg_t *msg ....." > > Am I correct in assuming this presents a dependency AMB has on Murphy? > Can someone help me understand what events Murphy fires to AMB?
Murphy uses basic information from AMB (such as speed, transmission, exterior brightness, ...) to be able to do decisions about the vehicle state. These decisions are then used for policing, such as regulating on-screen applications if the vehicle is moving. The processed states are then communicated back to AMB so that other applications can use the same information. At the moment Murphy controls "DrivingMode" and "NightMode" AMB properties. The control interface is the Murphy plugin that you have found from the AMB source code. So, to recap: from Murphy's point of view AMB is a source of system events and a place for propagating policy decisions to applications and other interested parties in the system. From AMB's point of view Murphy is a client for property changes and a provider of higher-level vehicle states. -- Ismo Puustinen <[email protected]> _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
