On 11/8/07, xasima <[EMAIL PROTECTED]> wrote: > Hi, Jerome and Alex. > > We can use http://smallx.dev.java.net or cocoon maps notation> > (http://cocoon.apache.org/2.2/core-modules/core/2.2/853_1_1.html) to provide > info for the coordination of such a pipes / URI. I think that reasons to do > this are > a) to get all advantages that cocoon offers by providing declarative URI model > and pipeline support > b) do the mentioned actions in distibuted manner, since each pipe can be > deployed in any place of the web (or in scope of your cluster), due to REST > notion of the pipe (GET, POST) and ability to negotiate on the representation > (JAVA_IN_PROCESS, SAX, DOM, or custom one).
It many ways, the use of URI templates in the API makes the API itself somewhat declarative. Being the person who started the smallx project, I'm not sure what you mean. I've been using Restlet for awhile now and it provides me a greater degree flexibility. Although, I have create my own set of XML configuration files for specifying virtual hosts and their applications. BTW, smallx has had a major change and is now available from two different google code projects: * http://code.google.com/p/xml-infoset * http://code.google.com/p/smallx The new version of smallx doesn't not contain all the XML infoset processing technology as that has been refactored into the xml-infoset project. All that remains in the smallx project is the XML pipelining technology--which has now moved forward to XProc (http://www.w3.org/TR/xproc/). My eventual plan is to provide an XProc integration with Restlet in the smallx project. --Alex Milowski
