Hi RAP devs, I'd like to give you an update on our plans for the next RAP release and make you aware of breaking API changes in this upcoming version.
As you all know, we've introduced a new open protocol [1] for the client-server communication in RAP 1.5. This protocol is currently used for responses (server-to-client) only. For the next release, we plan to extend the usage of the new protocol to the requests from client to server. When the protocol is used in both directions, we will also provide some new API for custom components based on the protocol. We plan to publish a new major version, RAP 2.0, in February 2013 to mark the completion of this restructuring. The plan for RAP 2.0 will be published on our website soon. With the update of the major version, we will also clean up some old API and discontinue the support of some obsolete features. This will lead to incompatible changes and require adjustments to all existing applications to work with RAP 2.0. After more than five years and seven releases, some cleanup seems to be necessary to allow us to continue progressing in a reasonable pace. The clean-up mostly affects API that is related to the old JavaScript-based protocol and/or very unlikely to be used by application code. As we don't plan to take any substantial functionality away, there will be replacements for most of the removed API. Unless you have built a lot of custom JavaScript widgets on the old protocol APIs, the migration will be smooth. And also for existing custom widgets, there is a straight-forward migration path. We've started a migration guide [2] to assist adjusting RAP 1.x applications for RAP 2.0. This guide will be updated during the development of RAP 2.0. If you have any questions or concerns, let us know. Regards, Ralf [1] http://wiki.eclipse.org/RAP/Protocol [2] http://eclipse.org/rap/noteworthy/2.0/migration-guide/ _______________________________________________ rap-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/rap-dev
