[news.eclipse.technology.ecf] Re: Relationship to KOI technology project

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

Hi Markus,

I believe that KOI could be used to implement the core ECF abstractions 
of a simple container (a lightweight container for communications 
applications) and a set of shared objects (communications components). 
KOI could easily provide a valid implementation of such a container.

That being said, I'm not sure what remains active of the KOI project.

One slight 'impedance mismatch' between KOI and ECF is that as I 
understand, KOI was based upon XML-RPC...which, although a fine protocol 
for client-server communications, doesn't scale well to peer-to-peer 
(multipoint) asynchronous messaging and scalable communications.  We 
think this makes it less well suited to some of the applications ECF is 
hoping to enable...e.g. peer-to-peer messaging, file sharing, IM, 
conferencing, etc.

But, like I said it should be possible to use KOI to implement the ECF 
container abstractions, and I hope that we and/or others would be able 
to do this.  If we can encourage or enable such an effort, we will do so.

Thanks,

Scott




)Markus Milleder wrote:
> Having read some overview documentation of ECF, I am left with the 
> impression that there is some overlap with the KOI project (where I have 
> also read some overview docs).
>
> Could you clarify the relationship between ECF and KOI - are ECF's needs 
> for collaboration so different from what KOI did that no reuse is 
> possible, or how much reuse will there be ?