You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-cvs@tcl.apache.org by mx...@apache.org on 2014/02/28 23:50:45 UTC

svn commit: r1573103 - in /tcl/rivet/branches/2.1: ChangeLog doc/xml/upgrade.xml

Author: mxmanghi
Date: Fri Feb 28 22:50:45 2014
New Revision: 1573103

URL: http://svn.apache.org/r1573103
Log:
* doc/xml/upgrading.xml: Adding Karl's note about upgrading from NeoWebScript

Modified:
    tcl/rivet/branches/2.1/ChangeLog
    tcl/rivet/branches/2.1/doc/xml/upgrade.xml

Modified: tcl/rivet/branches/2.1/ChangeLog
URL: http://svn.apache.org/viewvc/tcl/rivet/branches/2.1/ChangeLog?rev=1573103&r1=1573102&r2=1573103&view=diff
==============================================================================
--- tcl/rivet/branches/2.1/ChangeLog (original)
+++ tcl/rivet/branches/2.1/ChangeLog Fri Feb 28 22:50:45 2014
@@ -1,4 +1,6 @@
-<<<<<<< .mine
+2014-02-28 Massimo Manghi <mx...@apache.org>
+    * doc/xml/upgrading.xml: Adding Karl's note about upgrading from NeoWebScript
+
 2014-02-24 Massimo Manghi <mx...@apache.org>
     * doc/xml/commands.xml: completed reworking of manual page for command ::rivet::inspect.
     * .: Preparing RC1 archive for version 2.1.4

Modified: tcl/rivet/branches/2.1/doc/xml/upgrade.xml
URL: http://svn.apache.org/viewvc/tcl/rivet/branches/2.1/doc/xml/upgrade.xml?rev=1573103&r1=1573102&r2=1573103&view=diff
==============================================================================
--- tcl/rivet/branches/2.1/doc/xml/upgrade.xml (original)
+++ tcl/rivet/branches/2.1/doc/xml/upgrade.xml Fri Feb 28 22:50:45 2014
@@ -18,7 +18,33 @@
     </section>
     <section>
       <title>NeoWebScript</title>
-      <para>TODO</para>
+      <para>
+      	NWS was a server-side scripting environment based on the Apache
+        HTTP server and Safe-Tcl and it's not maintained anymore.      
+      </para>
+      <para>
+      	The biggest difference between Rivet and Neowebscript is that 
+      	Neowebscript was designed for shared hosting while Rivet is more oriented 
+      	toward a site that owns all of its content. In the words of Karl Lehenbauer,
+      	NWS author and Rivet Team member:
+      	</para> 
+      	<para>
+      	Rivet, however, is considerably more efficient, powerful, and 
+      	evolved, though it still can support multiple independent sites on a single 
+      	machine through its <quote>separate virtual interpreters</quote> mechanism.
+      	<itemizedlist>
+      		<listitem>By powerful, the difference is that the full power of Tcl is available 
+      		to webpage authors, not the restricted version that NWS provides. 
+      		For instance, you can read or write any file in the system that you 
+      		have permission to, require any package, open sockets and pipes, etc.</listitem>
+      		<listitem>By efficient, the difference is that Tcl interpreters survive past 
+      		the generation of a webpage and are reused again and again, reducing the 
+      		overhead of generating a page.
+      		</listitem>
+				<listitem>By evolved, all of our efforts have gone toward Rivet for many 
+				years and so, you know, Rivet does more out of the box than Neowebscript did.</listitem>
+			</itemizedlist>
+      </para>
     </section>
   </section>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: site-cvs-unsubscribe@tcl.apache.org
For additional commands, e-mail: site-cvs-help@tcl.apache.org