DBus usage for applications and services communication through servicemanager

[Ravi Kumar Kandati]

                SM(service manager) basically performs following activities after request received from apps.
                        1. Send the request to intended service.
                        2. Performs any pre-requisites required (i.e. stopping/pausing other functionalities. So SM will maintain the system state for pre-requisites processing) before processing the requests.

-----Original Message-----
From: Thiago Macieira [mailto:thiago at kde.org]
Sent: Friday, June 16, 2017 11:09 AM
To: Ravi Kumar Kandati <Ravikumar.Kandati at LntTechservices.com>
Cc: dbus at lists.freedesktop.org
Subject: Re: DBus usage for applications and services communication through servicemanager

On Thursday, 15 June 2017 22:10:09 PDT Ravi Kumar Kandati wrote:
> Are you suggesting single D-bus connection for SM. In this case there
> will be delay in processing priority requests when the applications
> and services increases.

Not really, since everything is already serialised via the D-Bus daemon. Even if you used multiple processes with each a dedicated connection, the daemon is the bottleneck.

In any case, you haven't explained what the SM does. You've only said it forwards the requests to other services. That is not a lot of processing, so doing everything in the same process, in one thread even, should not introduce a big bottleneck.

--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

L&T Technology Services Ltd

www.LntTechservices.com<http://www.lnttechservices.com/>

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.