[Babeldoc-devel] babeldoc/readme/userguide chapter1.xml,1.1.1.1,1.2

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/readme/userguide
In directory sc8-pr-cvs1:/tmp/cvs-serv25501/userguide

Modified Files:
	chapter1.xml 
Log Message:
Some small changes.

Index: chapter1.xml
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/readme/userguide/chapter1.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** chapter1.xml	24 Feb 2003 22:50:26 -0000	1.1.1.1
--- chapter1.xml	30 Jul 2003 23:24:06 -0000	1.2
***************
*** 11,16 ****
  			<para>Babeldoc can be used to process documents which are flowing in and out of a system.   There are three basic ways to develope applications to handle these document flows:</para>
  			<orderedlist>
! 				<listitem>Hand-coded standalone applications have the benefit of simplicity.   These applications can have be slow (java start-up times are significant) and also inflexible, hard to maintain, hard to track errors and can result in fragile systems. Also such systems are very non-portable.</listitem>
! 				<listitem>Hand-coded Rmi servers applications  better than (1) in terms of performance but can be hard to administer and control (you have to do this yourself).</listitem>
  				<listitem>Server based processes - this is better in manageability and terms of scaleability but could be overkill for simple situations.</listitem>
  			</orderedlist>
--- 11,16 ----
  			<para>Babeldoc can be used to process documents which are flowing in and out of a system.   There are three basic ways to develope applications to handle these document flows:</para>
  			<orderedlist>
! 				<listitem>Hand-coded standalone applications have the benefit of simplicity.   These applications can have be slow (java start-up times are significant) and also inflexible, hard to maintain, difficult to track errors and can result in fragile systems. Also such systems could be non-portable in that they make assumptions about their environments.</listitem>
! 				<listitem>Hand-coded Rmi (or similar protocol based) servers applications  better than (1) in terms of performance but can be hard to administer and control (you have to do this yourself).</listitem>
  				<listitem>Server based processes - this is better in manageability and terms of scaleability but could be overkill for simple situations.</listitem>
  			</orderedlist>
***************
*** 41,45 ****
  					<firstterm>Scanner</firstterm>: A standalone application to monitor resources (disks, FTP sites) and when a file is found, make a document and introduce the document to the specified pipeline.  This is a powerful tool and can be made to perform some intricate tasks.</listitem>
  				<listitem>
! 					<firstterm>Feeder</firstterm>: A standalone application that introduces a document into a pipeline.</listitem>
  			</orderedlist>
  		</section>
--- 41,47 ----
  					<firstterm>Scanner</firstterm>: A standalone application to monitor resources (disks, FTP sites) and when a file is found, make a document and introduce the document to the specified pipeline.  This is a powerful tool and can be made to perform some intricate tasks.</listitem>
  				<listitem>
! 					<firstterm>Feeder (1)</firstterm>: A standalone application that introduces a document into a pipeline.</listitem>
!         <listitem>
!           <firstterm>Feeder (2)</firstterm>: An internal babeldoc processing component that governs how documents are fed to pipelines.</listitem>
  			</orderedlist>
  		</section>