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

[Ferry Huberts]

On 24-05-12 12:23, Ferry Huberts wrote:
>
>
> On 24-05-12 11:39, Henning Rogge wrote:
>> On 05/24/2012 09:29 AM, Ferry Huberts wrote:
>>> From: Ferry Huberts<(spam-protected)>
>>>
>>> When the PUD plugin is loaded, displays the position
>>> information obtained from the PUD plugin, otherwise
>>> no position information is shown.
>>>
>>> As the PUD plugin is only available on Linux, the tab
>>> is (also) only available on Linux.
>>>
>>> Signed-off-by: Ferry Huberts<(spam-protected)>
>>
>> I admit I am not really happy with this, because the plugin suddenly
>> needs a change of the core. But I don't know a sane way to do this at
>> the moment.
>
> yeah, me too.
> Using something like a socket seemed waaaay overkill.
>
>
>>
>> Ferry, any suggestions how to do this in a generic way in the next
>> generation OLSRd?
>
> 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.
>


to clarify:
In OSGi a 'service' is a Java Interface. This is comparable to a C 
'header file'.
Nothing more, nothing less. This is key to understand.

>
> 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
>
>
> this combination would allow a plugin to query other plugins.
>
>
> this would be an excellent opportunity for a get-together on
> architecture ;-)
>
>>
>> Henning Rogge
>>
>
> so can I push the changes so that they'll be part of the next release?
>

-- 
Ferry Huberts