From 14730a133330573976fc1b14459984b7311ad0e5 Mon Sep 17 00:00:00 2001
From: mike <mike>
Date: Tue, 15 Nov 2005 17:33:04 +0000
Subject: [PATCH] Rolling.

---
 lib/ZOOM.pod |   15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/lib/ZOOM.pod b/lib/ZOOM.pod
index 83a55e3..cfb636e 100644
--- a/lib/ZOOM.pod
+++ b/lib/ZOOM.pod
@@ -1,4 +1,4 @@
-# $Id: ZOOM.pod,v 1.2 2005-11-15 17:23:45 mike Exp $
+# $Id: ZOOM.pod,v 1.3 2005-11-15 17:33:04 mike Exp $
 
 use strict;
 use warnings;
@@ -57,6 +57,19 @@ C<ZOOM::Query::PQF>.
 Many useful ZOOM applications can be built using only the Connection,
 ResultSet and Record classes, as in the example code-snippet above.
 
+A typical application will begin by creating an Connection object,
+then using that to execute searches that yield ResultSet objects, then
+fetching records from the result-sets to yield Record objects.  If an
+error occurs, an Exception object is thrown and can be dealt with.
+More sophisticated applications might browse the server's indexes to
+create a ScanSet, from which indexed terms may be retrieved; others
+might send ``Extended Services'' Packages to the server, to achieve
+non-standard tasks such as database creation and record update.
+Searching using a query syntax other than PQF can be done using an
+query object of one of the Query subclasses.  Finally, sets of options
+may be manipulated independently of the objects they are associated
+with using an Options object.
+
 
 =head1 SEE ALSO
 
-- 
1.7.10.4