[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[rap-dev] Proposal: "Remote Application Platform"
- From: Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Sep 2012 20:12:33 +0200
- Delivered-to: firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eclipsesource.com; s=eclipsesource; h=mime-version:from:date:message-id:subject:to:content-type; bh=RhGY7mj/j/XPP5IrO6r+k9aF2T0Js4hWbJREE/NbESI=; b=DLE2soYmgPTx4Lon13ZM5JOteQXoaQuLEeeJ7s6ITB1Bf6y60SjfGoW83IGUz26dnC F6FlCU4eZ+S/tVk2t0MqtvkKw6ZDGWepPluLqhrgwn2rE5zHr3316OcOHmmmAcquqxIJ NsamevWMmQiDSQlSdFQS67rj9w1eEyXmRGecA=
When the RAP project started 6 years ago, its main objective was to
provide a framework to make RCP applications available on the web. The
resemblance of the name "Rich Ajax Platform" to "Rich Client
Platform", was welcome back then as RAP was meant to complement RCP.
But over time, our focus has moved to more lightweight applications
and alternative clients like tablets and phones. Today this name does
not describe our project very well anymore. The term "rich" does not
reveal much information in itself and "Ajax" does not fit well for the
native clients, even though they still use HTTP. Ajax is more a
buzzword than a concise term anyway and as a buzzword, I think Ajax
has lost its appeal.
I recently found myself explaining RAP more often as a platform for
"remote applications" and I think this describes the idea very well.
It's essentially a platform for applications that run on a remote
server. With the new protocol and the alternative clients, this aspect
seems to become the central part of RAP.
Therefore I'd like to propose to relabel RAP to "Remote Application
Platform". This name would let us keep our short name, our namespace,
our website, etc. It wouldn't be a very noticable change, but we'd get
rid of the misleading name and highlight our technical approach
better. The 2.0 release in February 2013 may be a good occasion for
What do you think?