[news.eclipse.technology.ecp] Re: More on the project name, and relation

[wgehner@xxxxxxxxxxxx (Wolfgang Gehner)]

The RSP-UI proposal which Ed refers to is not published/submitted yet, so 
it's kinda hard to discuss in public. Hope to get it out there soon, 
though.

Only so much, there is good communication with ECP (including exchange of 
pre-proposal drafts), agreement to collaborate, and having integration 
points between ECP and RSP-UI. 

On ECF/OSGi console, Scott Lewis has confirmed interest to support and 
possibly contribute to RSP-UI, most likely through ECF usage/feedback.

Wolfgang Gehner

Ed Burnette wrote:

> 1. The RSP idea doesn't have to be tied to JEE. In fact I think that's a 
> bad idea and said so in my comments on the RSP proposal.
> 2. It shouldn't use legacy of Eclipse 2 unless there's some good reason to.
> 3. RSP is not a trademark. The '(tm)' thing was just a joke on 
> Wolfgang's part (I just asked him).
> 4. Rich Client Platform is well known. Changing 'client' to 'server' 
> just capitalizes on name recognition to quickly explain it, kind of like 
> the term 'cable modem'.

> You guys (you and Wolfgang and maybe Jeff McAffer) should really talk.

> I don't have any skin in this but I think Eclipse needs something really 
> low level, simple, and flexible to serve as a legacy-free framework for 
> server applications of the future. Namely, equinox on the server, with 
> dynamic bundles and services and all that implies. See also my 'grand 
> challenges' talk at EclipseCon, and the neat ECF/OSGi console that Scott 
> Lewis did.


> Alex Antonau wrote:
> > We familiar with the Rich Server Platform but there are essential 
> > differences:
> > 1. RSP is just a plug-in system for JEE container
> > 2. RSP uses legacy of Eclipse 2 ? Eclipse extension points
> > 3. RSP name is a trademark
>  > 4. "Rich" is not commonly used term in
> > enterprise application development and could arise questions
> >
> > Alex Antonau