| Re: [iot-wg] IoT Server Platform |
Hi Kai,
On 9/11/2015 1:26 AM, Hudalla Kai (INST/ESY) wrote:
> Hi Scott,
>
> thanks for your reply. I have made some comments below ...
>
>> ECF's implementation of OSGi Remote Services/Remote Service Admin [2]
>> is clearly technically related to IoT Server Platform work and IoT more
>> generally, and we've articulated some of those technical connections
>> here [3]. Further, I'm aware of several cloud-based products
>> successfully using ECF's RSA implementation right now.
>>
> Thanks for pointing this out. The ECF certainly could be a valuable component for implementing an IoT Server Platform.
> I am by no means an expert in ECF and I wonder whether ECF's protocol implementations can also be used outside of
> an OSGi framework and using strict messaging semantics, i.e. in a message exchange pattern not necessarily implementing
> a remote service invocation but instead simple message forwarding?
Yes. There are several transport providers that can be used outside of
OSGi. e.g. the generic provider (which I use myself in Android
environments, for example), the JMS provider, the MQTT provider, the
Jax-RS providers, the Hazelcast provider.
You also appear to be asking about support for publish/subscribe
messaging patterns (as opposed to RPC/remote service patterns). The
answer to this is also a strong 'yes', as this work implementing
distributed event admin demonstrates [1]. I can also tell you that the
model underlying the generic provider and several of the other providers
(JMS, MQTT, etc) is based upon an asynchronous multipoint (pub/sub)
messaging approach, so any of these can be used directly in this manner
without the RSA impl bundles. With respect to standardization, OSGi
RFP-158 is on distributed eventing [2]. I am participating in the EEG
around these directions.
>
> While OSGi is surely an option for implementing server side components, my personal feeling is that server side components
> will be implemented using arbitrary technologies and deployment models beyond OSGi as well.
I certainly agree with you about that. FWIW, there is some work I've
recently done to use Apache Connect to expose remote services in
Java-only environments (no OSGi framework) [2]. Apache Connect is an
implementation of the OSGi Service Registry...without the underlying
OSGi framework. Since Renote Services/RSA is simply an extension to
the OSGi Service Registry, ECF's impl...and any remote services...run
unmodified on Java-only runtimes.
>
>> There is a bit of a problem, however, in that as much as ECF would like
>> to participate in the EF IoT Server Platform work, we are currently
>> somewhat process-limited in how much we can contribute because we are
>> not sponsored or supported by an IoT working group company. For the
>> record, we would welcome committers/contributors to ECF from the IoT
>> working group.
>>
> That is good to hear :-)
> I think we should start to discuss opportunities where we could mutually benefit from each other's collaboration.
Sure. That would be splendid.
> A first connection point might be integration of ECF and Kura?
That would be great. I've suggested it several times on this mailing
list and on the kura-dev mailing list, and would still very much like to
have it happen. ECF's RSA implementation runs now on any R5-compliant
impl of the framework (e.g. Karaf/Felix as well as Equinox).
>
>> It is possible that some of ECF's Europe-based committers will attend
>> EclipseCon 2015, if they are able to attend I'm sure they would be
>> happy to participate.
>>
> That would be great, I'm looking forward to meet any of you guys there!
I will encourage our ECF-Europe committers to attend.
Scott
[1] https://wiki.eclipse.org/Distributed_EventAdmin_Service
[2] https://github.com/osgi/design/tree/master/rfps
[3] https://github.com/ECF/ServiceRegistry
_______________________________________________
iot-wg mailing list
iot-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-wg