[audio-manager] Queueing of back to back connect commands

Nithya.K nithya.k at jasmin-infotech.com
Tue Jan 10 01:22:23 EST 2017


Hi Christian and Toshiaki Isogai, 

Thank you for your response. 

We are currently working with the generic controller. The queuing that is mentioned in the response mail refers to the trigger queue, we believe. 

As per our understanding, the trigger queue is filled with next command request, only after 1 child action corresponding to the current trigger is dispatched to the routing adapter. Also, only when the action queue is empty (i.e, all child actions corresponding to current trigger are executed), the next trigger is dequeued and forwarded to policy engine. 

Due to this behavior, the queuing in controller does not happen in the same speed at which the source switch requests are given to the command plugin from HMI. For eg., we might have given 10 source switch requests from HMI but by this time there could be only 3 or 4 triggers filled in the trigger queue. Hence, we are not sure if logic implemented at this level for skipping some source switch requests, would work as expected. (i.e, not all intermediate source switches would be skipped.) 

Please share your thoughts on this. 

Thanks & Regards, 
Nithya K 
Principal Engineer 
Jasmin Infotech Pvt Ltd 
Tel: +91-44-30619600, Extn: 1023 



----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

Information in this email is proprietary and Confidential to Jasmin Infotech. Any use, copying or dissemination of the information in any manner is strictly prohibited. 

If you are not the intended recipient, please destroy the message and please inform to us. 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 


From: "Toshiaki ISOGAI" <isogai.toshiaki at nttd-mse.com> 
To: "Christian Linke" <Christian.Linke at bmw.de>, "nithya k" <nithya.k at jasmin-infotech.com>, "genivi-audio-manager" <genivi-audio-manager at mailman1.genivi.org> 
Sent: Monday, January 9, 2017 3:34:49 PM 
Subject: RE: [audio-manager] Queueing of back to back connect commands 



Hi, 



Generic Controller currently implements queueing the request from command side. 

And “ connect ” API is asynchronously processed after it returns to application. 

Result will be notified by cbMainConnectionStateChanged(). 



But current implementation does not have option to remain only the latest one in queue during processing, meaning does not skip intermediate requests between current and latest. 

All requests in queue will be processed by stored order. 



Therefore performance of switching source is depending on the response from routing side. 



Best regards, 

Toshiaki Isogai 




From: genivi-audio-manager [mailto:genivi-audio-manager-bounces at mailman1.genivi.org] On Behalf Of Christian.Linke at bmw.de 
Sent: Monday, January 09, 2017 6:36 PM 
To: nithya.k at jasmin-infotech.com; genivi-audio-manager at mailman1.genivi.org 
Subject: Re: [audio-manager] Queueing of back to back connect commands 




Hi, 



All connect commands end up in the controller. There, you can implement in the project specific part a handling that does the queuing of the commands like you need it to. 

(We do the same J ). 



So it’s possible to do that, but you need to do it yourself J 



For the generic controller, I do not know, can somebody please state on that? 



Christian 






Von: genivi-audio-manager [ mailto:genivi-audio-manager-bounces at mailman1.genivi.org ] Im Auftrag von Nithya.K 
Gesendet: Donnerstag, 22. Dezember 2016 11:49 
An: genivi-audio-manager at mailman1.genivi.org 
Betreff: [audio-manager] Queueing of back to back connect commands 





Hi Team, 





We are currently working on a project based on Genivi Audio Manager (v7.4). CommonAPI is being used to interface the command and routing plugins with external world. CommonAPI is registered in the audiomanager mainloop (am::CAmSocketHandler). 





There is a requirement for queuing back to back connect commands from HMI & processing only the last one, in case there is a very fast switching of sources from HMI. Can you please let us know if this handling is been done in Genivi Audio Manager? 





As per our knowledge, all the APIs for 'connect', right from the command plugin until the routing plugin are synchronous. Hence, we are unable to locate the exact point where this queuing of connect commands can be handled within the Audio Manager. 





Please provide your inputs on this. 





Thanks & Regards, 
Nithya K 
Principal Engineer 
Jasmin Infotech Pvt Ltd 
Tel: +91-44-30619600, Extn: 1023 





----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

Information in this email is proprietary and Confidential to Jasmin Infotech. Any use, copying or dissemination of the information in any manner is strictly prohibited. 

If you are not the intended recipient, please destroy the message and please inform to us. 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genivi.org/pipermail/genivi-audio-manager_lists.genivi.org/attachments/20170110/1275308f/attachment.html>


More information about the genivi-audio-manager mailing list