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

[Ed Burnette <ed.burnette@xxxxxxx>]

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