Hi,
> 2. Creating ONE Tizen specific gSSO plugin and use this plugin
> to load all Tizen authenticator plugins. So basically this would have
> worked like a plugin loader,
I would propose to do a variant of this. So you could implement a custom
Tizen specific plugind (the daemon/shim that loads and runs plugin
instances). Since the interface between gsignond and plugind is dbus
interface, it allows you to use what ever kind of API towards plugins.
The plugind is just loader and translator between dbus and plugin
interfaces.
What we would need to change in upstream gsignond is to support multiple
plugind's and to know which one to use for each plugin. For that we
could add configuration entry to define additional plugind's and
corresponding plugin directories.
I think this is cleanest way to achieve glib isolation. It would allow
writing plugind and/or plugins even in different language like Python.
You could also base the work on the currently existing plugind code and
just replace the actual plugin interface there.
Best regards,
- Jussi
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
