projects
/
irspy-moved-to-github.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
665545d
)
Tweak comment.
author
Mike Taylor
<mike@indexdata.com>
Wed, 14 Mar 2007 11:56:35 +0000
(11:56 +0000)
committer
Mike Taylor
<mike@indexdata.com>
Wed, 14 Mar 2007 11:56:35 +0000
(11:56 +0000)
lib/ZOOM/IRSpy/Task/Search.pm
patch
|
blob
|
history
diff --git
a/lib/ZOOM/IRSpy/Task/Search.pm
b/lib/ZOOM/IRSpy/Task/Search.pm
index
da0fc29
..
397dbee
100644
(file)
--- a/
lib/ZOOM/IRSpy/Task/Search.pm
+++ b/
lib/ZOOM/IRSpy/Task/Search.pm
@@
-1,4
+1,4
@@
-# $Id: Search.pm,v 1.12 2007-03-13 16:12:38 mike Exp $
+# $Id: Search.pm,v 1.13 2007-03-14 11:56:35 mike Exp $
package ZOOM::IRSpy::Task::Search;
package ZOOM::IRSpy::Task::Search;
@@
-46,12
+46,12
@@
sub run {
" searching for '$query'");
die "task $this has resultset?!" if defined $this->{rs};
" searching for '$query'");
die "task $this has resultset?!" if defined $this->{rs};
- ### NOTE WELL that when this task runs, it creates a result-set
+ ### Note well that when this task runs, it creates a result-set
# object which MUST BE DESTROYED in order to prevent large-scale
# memory leakage. So when creating a Task::Search, it is the
# APPLICATION'S RESPONSIBILITY to ensure that the callback
# object which MUST BE DESTROYED in order to prevent large-scale
# memory leakage. So when creating a Task::Search, it is the
# APPLICATION'S RESPONSIBILITY to ensure that the callback
- # invoked on success makes arrangements for the set to be
- # destroyed.
+ # invoked on success OR FAILURE makes arrangements for the set
+ # to be destroyed.
$this->{rs} = $conn->search_pqf($query);
warn "no ZOOM-C level events queued by $this"
if $conn->is_idle();
$this->{rs} = $conn->search_pqf($query);
warn "no ZOOM-C level events queued by $this"
if $conn->is_idle();