From 1a18b079807428305b7376022236e901e4f576ca Mon Sep 17 00:00:00 2001 From: mike Date: Tue, 11 Apr 2006 16:40:08 +0000 Subject: [PATCH] Tweaks. --- lib/ZOOM.pod | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/lib/ZOOM.pod b/lib/ZOOM.pod index 908bba5..fd8abbf 100644 --- a/lib/ZOOM.pod +++ b/lib/ZOOM.pod @@ -1,4 +1,4 @@ -# $Id: ZOOM.pod,v 1.32 2006-04-11 16:38:38 mike Exp $ +# $Id: ZOOM.pod,v 1.33 2006-04-11 16:40:08 mike Exp $ use strict; use warnings; @@ -1377,12 +1377,12 @@ The approach is as follows: Create several connections to the various servers, each of them having the option C set, and with whatever additional options are -required - e.g. setting the piggyback retrieval record-count so that -records will be returned in search responses. +required - e.g. the piggyback retrieval record-count can be set so +that records will be returned in search responses. =item Operations -Send searches to the connections, request record retrieval, etc. +Send searches to the connections, request records, etc. =item Event harvesting @@ -1391,8 +1391,8 @@ received from the servers. Each time this function returns, it indicates which of the connections has fired; this connection can then be interrogated with the C method to discover what event has occurred, and the return value - an element of the C -enumeration can be used to determine what to do next. For example, -the C operation indicates that no further operations are +enumeration - can be tested to determine what to do next. For +example, the C event indicates that no further operations are outstanding on the connection, so any fetched records can now be immediately obtained. -- 1.7.10.4