You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by jo...@apache.org on 2001/03/05 02:56:39 UTC
cvs commit: jakarta-velocity/docs/ymtd ymtd-changes.html ymtd-implementation.html
jon 01/03/04 17:56:39
Modified: xdocs/ymtd ymtd-changes.xml ymtd-implementation.xml
docs/ymtd ymtd-changes.html ymtd-implementation.html
Log:
cleanup of the way the implementation page was written
Revision Changes Path
1.3 +3 -0 jakarta-velocity/xdocs/ymtd/ymtd-changes.xml
Index: ymtd-changes.xml
===================================================================
RCS file: /home/cvs/jakarta-velocity/xdocs/ymtd/ymtd-changes.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ymtd-changes.xml 2001/03/05 00:06:12 1.2
+++ ymtd-changes.xml 2001/03/05 01:56:39 1.3
@@ -19,6 +19,9 @@
<p>
<ul>
+<li>Cleanup of the way that the <a
+href="./ymtd-implementation.html">Implementation</a> page
+is written in order to clarify the points.</li>
<li>Minor clarification in the <a
href="./ymtd-saying-hello.html">Saying Hello</a> example.</li>
<li>Added the <a href="./ymtd-hosting.html">Hosting</a> page to address
1.3 +21 -9 jakarta-velocity/xdocs/ymtd/ymtd-implementation.xml
Index: ymtd-implementation.xml
===================================================================
RCS file: /home/cvs/jakarta-velocity/xdocs/ymtd/ymtd-implementation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ymtd-implementation.xml 2001/03/04 23:16:08 1.2
+++ ymtd-implementation.xml 2001/03/05 01:56:39 1.3
@@ -19,7 +19,7 @@
reality of this statement reveals that the important correct terminology
is that JSP is a "Sun Standard Specification" and not strictly a
"standard." This is important because JSP is really no more "standard"
-than Micro$oft ASP or the PHP Group's PHP product. In other words,
+than Microsoft ASP or the PHP Group's PHP product. In other words,
whatever tool you happen to be using becomes the "standard."
</p>
@@ -32,6 +32,17 @@
proprietary product of Sun!
</p>
+<p>
+It is important to note at this point that the primary author of this
+document (Jon Stevens) is a member of the JSR-053 which defines the
+Servlet and JSP specification's.
+</p>
+
+<p>
+Inside JSR-053, it is clear that not everything is done in the open and
+decisions are made behind closed doors. Of course the participants could
+object, but Sun still is the binding force behind the decisions.
+</p>
</subsection>
<subsection name="The next point: Complexity">
@@ -70,20 +81,21 @@
<subsection name="The final point: Velocity">
<p>
-Even though Velocity is lacking a specification document (it is on the
-TODO list and volunteers are welcome to help out) and is not a "Sun
-Specification Standard" (although it probably could be, but would it be
-really worth it?), that should not stop anyone from using it in
-production environments. The reason is that as shown above, the fact of
-the matter is that JSP is no more of a "standard" than anything else.
+Even though Velocity is lacking a formal specification document (it is
+on the TODO list and volunteers are welcome to help out) and is not a
+"Sun Specification Standard", that should not stop anyone from using it
+in production environments. The reason is that, as shown above, is that
+JSP is no more of a "standard" than anything else.
</p>
<p>
-Velocity is actually a more reliable implementation because there is
-currently only one implementation, the modifications to the code base
+Velocity is actually a more reliable implementation than JSP because
+there is currently only one implementation. Even if there were more
+implementations the modifications to all aspects of the Velocity project
are discussed in the open (anyone is welcome to participate) and the
testing suite is strictly maintained.
</p>
+
</subsection>
<p>
1.4 +2 -0 jakarta-velocity/docs/ymtd/ymtd-changes.html
Index: ymtd-changes.html
===================================================================
RCS file: /home/cvs/jakarta-velocity/docs/ymtd/ymtd-changes.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ymtd-changes.html 2001/03/05 00:23:30 1.3
+++ ymtd-changes.html 2001/03/05 01:56:39 1.4
@@ -110,6 +110,8 @@
</p>
<p>
<ul>
+<li>Cleanup of the way that the <a href="./ymtd-implementation.html">Implementation</a> page
+is written in order to clarify the points.</li>
<li>Minor clarification in the <a href="./ymtd-saying-hello.html">Saying Hello</a> example.</li>
<li>Added the <a href="./ymtd-hosting.html">Hosting</a> page to address
the idea that JSP makes a great hosting platform.</li>
1.5 +19 -9 jakarta-velocity/docs/ymtd/ymtd-implementation.html
Index: ymtd-implementation.html
===================================================================
RCS file: /home/cvs/jakarta-velocity/docs/ymtd/ymtd-implementation.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- ymtd-implementation.html 2001/03/05 00:23:33 1.4
+++ ymtd-implementation.html 2001/03/05 01:56:39 1.5
@@ -117,7 +117,7 @@
reality of this statement reveals that the important correct terminology
is that JSP is a "Sun Standard Specification" and not strictly a
"standard." This is important because JSP is really no more "standard"
-than Micro$oft ASP or the PHP Group's PHP product. In other words,
+than Microsoft ASP or the PHP Group's PHP product. In other words,
whatever tool you happen to be using becomes the "standard."
</p>
<p>
@@ -128,6 +128,16 @@
stretch as far as to say that the JSP specification is really a
proprietary product of Sun!
</p>
+ <p>
+It is important to note at this point that the primary author of this
+document (Jon Stevens) is a member of the JSR-053 which defines the
+Servlet and JSP specification's.
+</p>
+ <p>
+Inside JSR-053, it is clear that not everything is done in the open and
+decisions are made behind closed doors. Of course the participants could
+object, but Sun still is the binding force behind the decisions.
+</p>
</blockquote>
</td></tr>
</table>
@@ -177,16 +187,16 @@
<tr><td>
<blockquote>
<p>
-Even though Velocity is lacking a specification document (it is on the
-TODO list and volunteers are welcome to help out) and is not a "Sun
-Specification Standard" (although it probably could be, but would it be
-really worth it?), that should not stop anyone from using it in
-production environments. The reason is that as shown above, the fact of
-the matter is that JSP is no more of a "standard" than anything else.
+Even though Velocity is lacking a formal specification document (it is
+on the TODO list and volunteers are welcome to help out) and is not a
+"Sun Specification Standard", that should not stop anyone from using it
+in production environments. The reason is that, as shown above, is that
+JSP is no more of a "standard" than anything else.
</p>
<p>
-Velocity is actually a more reliable implementation because there is
-currently only one implementation, the modifications to the code base
+Velocity is actually a more reliable implementation than JSP because
+there is currently only one implementation. Even if there were more
+implementations the modifications to all aspects of the Velocity project
are discussed in the open (anyone is welcome to participate) and the
testing suite is strictly maintained.
</p>