Page: http://wiki.cocoondev.org/Wiki.jsp?page=SimilarServers , version: 29 on 
Sun Apr 13 16:52:58 2003 by 212.198.0.97

+ *__[Whitebeam|http://www.whitebeam.org/]__
+ ''is an Open Source project that provides a complete rapid development 
environment and web application server allowing sophisticated, robust and 
secure applications to be built using only XML and server-side JavaScript.
+ 
+ The Whitebeam architecture integrates two popular and robust Open Source 
platforms - Apache and Mozilla's SpiderMonkey JavaScript engine - with it's own 
powerful XML environment and security architecture. The XML environment 
provides both event driven and DOM based manipulation of XML trees along with 
the powerful XPath querying language - all controlled via simple server-side 
JavaScript interface.
+ 
+ Whitebeam provides an extensible XML based interface to back end objects on 
any platform, the client model securely segregates thousands of customer 
applications within a single server. Interfaces currently exist to IBM DB2, 
Postgres, INN (News Service), SMTP (email) and HTTP (to access SOAP etc)''
+ 
+ *__[Murka|http://murka.sourceforge.net/]__
+ ''Murka is an apache module (mod_murka). It intercepts an http request at a 
very early stage of apache request processing and if the requested file has 
.html or .jsp type performs the following steps:
+ 1. Checks if file exists. If it exists returns control to standard apache 
request processing.
+ 2. If the file does not exist looks for xml file in the same directory and 
with the same name (but with .xml extension). For example if the request file 
had a name sample.html the xml file name would be sample.xml.
+ 3. Processes the xml file to find the location of the corresponding xsl 
stylesheet.
+ 4. Calls one of the XSLT engines (Xalan or Sablotron) with found xml and xsl 
files as parameters to produce an html file.
+ 5. Saves html file at the requested location (sample.html in the sample case).
+ 6. Returns control to apache
+ Next time when the same html file is requested it would exist as a plain html 
and no murka processing would be necessary. The above procedure results in 
implicit html cache building for all requested html files. If any of the xml 
data files or presentation stylesheet xsl files changes, one just needs to 
delete the corresponding html file (clear cache) and murka would build the 
updated html file automatically.
+ ''
+ 


Page: http://wiki.cocoondev.org/Wiki.jsp?page=Tutorials , version: 30 on Sun 
Apr 13 16:00:33 2003 by StephanNiedermeier

- * [Cocoon 2 
Tutorial|http://www.logabit.com/consulting/cocoon/CocoonTutorial.html] -- an 
introduction to Cocoon 2 and some little tutorials. (This tutorial is not 
complete yet.)
?                                               -----------    ^^^^^^^^         
^^^

+ * [Cocoon 2 Tutorial|http://www.logabit.com/cocoontutorial.php] -- an 
introduction to Cocoon 2 and some little tutorials. (This tutorial is not 
complete yet.)
?                                                   ^        + ^



Reply via email to