[news.eclipse.technology.spaces] Re: Consider ECF

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

I do hope the spaces project can find a way to use some of the ECF APIs. 
 We've already developed APIs needed for sharing arbitrary resources 
(e.g. asynch file transfer, serialized object/model replication, 
authentication/access control to a distributed group, support for 
pluggable transport protocols, unique identifiers within Namespaces [and 
extension point for introducing new namespaces], exstensible clients for 
IRC/XMPP/Yahoo/MSN IM/Chat, bulletin board API w NNTP support, new Skype 
provider (for IM/chat/skype VOIP), remote workspace control, shared 
editors, etc).

Also, the Equinox provisioning incubator project

http://www.eclipse.org/equinox/incubator/provisioning/

is using ECF's asynch file transfer API...because it has pluggable 
protocol support (ftp, bittorrent, http/https, etc) and runs on nearly 
all execution environments (CDC 1.0/Foundation 1.0).

It would be quite a waste if the spaces project were to redevelop these 
or introduce new mechanisms doing the same things.

Please let us know if we can help.  ecf-dev@xxxxxxxxxxx or me at 
slewis@xxxxxxxxxxxxxx

Scott

ECF Project Lead

Scott Lewis wrote:
> +2 to this :)
>
> Erkki Lindpere wrote:
> > Hi!
> >
> > If you are including Chat, Forums and Newsgroups in the scope, you 
> > should consider ECF as an applicable Eclipse technology. It includes 
> > the Presence API and Chat for instant messaging, and a Bulletin Board 
> > API is incubating (a work in progress), which can currently access 
> > vBulletin and phpBB forums (using "web scrapers") and I've started 
> > work privately on an NNTP provider for accessing newsgroups through 
> > the same API.
> >
> > Erkki Lindpere