[srm-cvs] CVS Update: - More textual updates

Date: Mon Feb 18 07:36:10 CET 2002
User: Dan Kalowsky
Directory: srmdoc/user

Log Message:
 [0.98]
 - More textual updates
 # Not entirely happy with that last paragraph at all. Comments and reviews
 # on it would be appriciated
 
Modified files:
           srmdoc/user/intro.xml (version: 1.6)

[FILE: /srmdoc/user/intro.xml]

--- srmdoc/user/intro.xml:1.5 Tue Feb 12 10:02:55 2002 GMT
+++ srmdoc/user/intro.xml Mon Feb 18 05:36:08 2002 GMT
@@ -6,23 +6,26 @@
  <para>
   Vulcan Logic's Script Running Machine, SRM, was first conceived in the
   autumn of 2000. It is designed to solve some of the problems often
- encountered with PHP and other web scripting languages that result from the
- statelessness of the HTTP protocol.
+ encountered within web scripting languages (i.e. PHP) that are a result
+ of the stateless nature of the HTTP protocol.
  </para>
  <para>
- SRM will use various methods to cope with the problems presented to
- programmers. It will offer caching of variables directly from supported
- scripting languages, and as they will be held in memory there will be
- considerable speed increases over a database-only approach.
+ SRM utilizes various methods to cope with the problems presented to
+ programmers, such as the direct caching of variables from supported
+ scripting languages. This approach offers a considerable increase in speed
+ over a database-only solution, mainly due to speed the SRM system keeping
+ the values in memory.
+ <!-- but why? -Dan -->
  </para>
  <para>
- Another feature of SRM will be it's ability to handle all database
- connections persistently; this will offer significant advantages in a variety
- of situations where you are either using multiple supported scripting
- languages or want to be able to control the amount of connections spawned to
- your database server in a more effective way. SRM does not spawn a connection
- to your database server for each connection but decides whether it is worth
- it or if it is better to share another connection.
+ Another feature of SRM is it's ability to handle all persistent database
+ connections, offering a significant advantage in a variety of
+ situations. The SRM system can give a developer the ability to support the
+ use of multiple scripting languages, or the ability to control the
+ number of connections spawned to a database server more effectively.
+ The SRM system does not spawn a connection to a database server for each
+ individual connection, but rather it can decide if it is worth the overhead
+ or if it is better to share another connection.
  </para>
 </chapter>
 <!-- keep this comment at the end of the file
Received on Mon Feb 18 07:28:36 2002