Read-only archive of the All About Symbian forum (2001–2013) · About this archive

Capabilities and ecom plugins

1 replies · 0 views · Started 14 August 2006

Imagine the following scenario:

- One server whose sole purpose is managing settings which are required
by several programs (gui applications and other servers). The setting
file is stored in the server's private directory.

- One server that works with some critical apis, requiring capabilities
such as NetworkControl, MultimediaDD, etc.
This server is a client of the settings server, as it needs to retrieve
some settings. This makes the setting's dll to have these capabilities
(NetworkControl, etc) as a minimum.

- An ecom plugin implementation (defined by some system server) which
also needs access to these settings. The problem is that the needed
capabilities aren't probably supported by the system server.

Is there any elegant solution to this? So far the only way I can think
of is embedding some of the setting server functionality in the plugin.
Of course, the setting file would no longer be in a private directory.

--
David Caabeiro
www.PushL.com

> Imagine the following scenario:
>
> - One server whose sole purpose is managing settings which are required by
> several programs (gui applications and other servers). The setting file is
> stored in the server's private directory.
>
> - One server that works with some critical apis, requiring capabilities
> such as NetworkControl, MultimediaDD, etc.
> This server is a client of the settings server, as it needs to retrieve
> some settings. This makes the setting's dll to have these capabilities
> (NetworkControl, etc) as a minimum.
>
> - An ecom plugin implementation (defined by some system server) which also
> needs access to these settings. The problem is that the needed
> capabilities aren't probably supported by the system server.
>
> Is there any elegant solution to this? So far the only way I can think of
> is embedding some of the setting server functionality in the plugin. Of
> course, the setting file would no longer be in a private directory.

Replying to myself, this is actually quite easy. Just use a second client
dll with less capabilities. Of course, the server will need to take this
into account in his access policy, to only allow access from trusted
apps/vendors/etc.

David.-