You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by jt...@apache.org on 2006/03/21 04:07:10 UTC

svn commit: r387386 - in /db/derby/site/trunk: build/site/papers/DerbyTut/ns_intro.html src/documentation/content/xdocs/papers/DerbyTut/ns_intro.xml

Author: jta
Date: Mon Mar 20 19:07:07 2006
New Revision: 387386

URL: http://svn.apache.org/viewcvs?rev=387386&view=rev
Log:
DerbyTut: Previously I had removed bogus references to sysinfo connecting
to a database in the figures. Just now spotted and removed more bogus
references in the text.

Modified:
    db/derby/site/trunk/build/site/papers/DerbyTut/ns_intro.html
    db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/ns_intro.xml

Modified: db/derby/site/trunk/build/site/papers/DerbyTut/ns_intro.html
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/build/site/papers/DerbyTut/ns_intro.html?rev=387386&r1=387385&r2=387386&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/papers/DerbyTut/ns_intro.html (original)
+++ db/derby/site/trunk/build/site/papers/DerbyTut/ns_intro.html Mon Mar 20 19:07:07 2006
@@ -643,7 +643,8 @@
 <span class="codefrag">MyEmbedSrvApp</span> that loads the embedded driver and also
 starts up the Network Server.
 This allows other applications,
-such as <span class="codefrag">ij</span> and <span class="codefrag">sysinfo</span>,
+such as <span class="codefrag">ij</span>
+or <span class="codefrag">SimpleApp</span> using the Derby Network Client,
 to connect to the same database <em>via</em> a client JDBC driver.
 </p>
 <p>
@@ -660,14 +661,14 @@
 for <span class="codefrag">MyEmbedSrvApp</span> 
 to use the Derby Network Client JDBC driver, 
 it's probably better for it to use the embedded driver
-because Derby Network Client JDBC database requests will incur the
+because Derby Network Client JDBC database requests incur the
 overhead of going out through the network.
 The embedded server architecture lets
 the application that embeds Derby retain the advantages of
 embedded access while
 also enabling remote access to the same database using another tool,
-such as <span class="codefrag">ij</span> or <span class="codefrag">sysinfo</span>.
-So, you end up with the best of both worlds: embedded and client/server.
+such as <span class="codefrag">ij</span>.
+Thus, you end up with the best of both worlds: embedded and client/server.
 </p>
 <p>
 You've reached the end of this Derby tutorial and should now understand

Modified: db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/ns_intro.xml
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/ns_intro.xml?rev=387386&r1=387385&r2=387386&view=diff
==============================================================================
--- db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/ns_intro.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/papers/DerbyTut/ns_intro.xml Mon Mar 20 19:07:07 2006
@@ -440,7 +440,8 @@
 <code>MyEmbedSrvApp</code> that loads the embedded driver and also
 starts up the Network Server.
 This allows other applications,
-such as <code>ij</code> and <code>sysinfo</code>,
+such as <code>ij</code>
+or <code>SimpleApp</code> using the Derby Network Client,
 to connect to the same database <em>via</em> a client JDBC driver.
 </p>
 
@@ -456,14 +457,14 @@
 for <code>MyEmbedSrvApp</code> 
 to use the Derby Network Client JDBC driver, 
 it's probably better for it to use the embedded driver
-because Derby Network Client JDBC database requests will incur the
+because Derby Network Client JDBC database requests incur the
 overhead of going out through the network.
 The embedded server architecture lets
 the application that embeds Derby retain the advantages of
 embedded access while
 also enabling remote access to the same database using another tool,
-such as <code>ij</code> or <code>sysinfo</code>.
-So, you end up with the best of both worlds: embedded and client/server.
+such as <code>ij</code>.
+Thus, you end up with the best of both worlds: embedded and client/server.
 </p>
 </section>