[Olsr-dev] [PATCH v3 1/2] httpinfo: add position information tab

Henning Rogge (spam-protected)
Thu May 24 12:48:41 CEST 2012

On 05/24/2012 12:23 PM, Ferry Huberts wrote:
> yeah, me too.
> Using something like a socket seemed waaaay overkill.


> yes, use OSGi declarative services.
> seriously, the ideas in OSGi declarative services are extremely valid:
> If we have plugins provide certain 'service interfaces' and we have a
> way of accessing the plugins, we can sort-of safely do what we want.
> we need more information in the core to determine what the
> type/name/id/provides services/... of the loaded plugins are.

Maybe there is a way to adapt this concept in a lightweight way.

> the 'service interfaces' I thinking about are:
> - init/start/stop/unint (like we have not) (mandatory)
> - identification (mandatory)
> - provides services (mandatory)
> - configuration (optional)
> - ... anything more we need

At the moment the new framework has four callbacks (which can be used by 
the plugin): init, enable, disable and "remove".

It also has a struct with the plugins name, description and author.

A configuration callback is not necessary because the plugins will be 
using their init callback to hook their own configuration into the 
central config management (with a function of the core) if necessary.

If the plugin supply a list of function names it exports to other parts 
of the framework, the plugin loader could supply pointers for this 

Henning Rogge

Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961,   Fax +49 228 9435 685
mailto:(spam-protected) http://www.fkie.fraunhofer.de
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6156 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20120524/0bd568c7/attachment.bin>

More information about the Olsr-dev mailing list