Hello, > 1) Coocoon map concept > (http://cocoon.apache.org/2.2/core-modules/core/2.2/1376_1_1.h > tml), just to > provide more declarative way to configure URI - Restlets mapping?
In Restlet 1.1, we'll introduce the support for more declarative XML configurations based on WADL and probably an additional custom XML file. See related issues: WADL support: http://restlet.tigris.org/issues/show_bug.cgi?id=59 XML configuration: http://restlet.tigris.org/issues/show_bug.cgi?id=164 > 2) Internal Restful design of web-application? means to get > name for each of the > individual classes/resources/restlet with the help of java5 > annotation > @uri("schema://internal/weatherwidgetresource") > and use them as individual pipes (POST data to proccess and > getTheRepresentation > of the result) [...] Good points, and I think 1.1 will please you because we'll have new related features: 1) The ability to internally dispatch requests without going thought the network layers (no IO for representations): http://restlet.tigris.org/issues/show_bug.cgi?id=157 2) The support of a private and internal access scheme (ex: "riap://component/myAppPath/myResource") that will allow modularization of applications and efficient composition of resources via XSLT or other means. This is inspired from Cocoon pseudo-protocols: http://restlet.tigris.org/issues/show_bug.cgi?id=374 Best regards, Jerome
