11th February 2002
Started: 25th September 2001
Last update: 11th February 2002
The Net::Z3950 module requires the servers to which it
connects to support named result sets, which functionality turns out
not to be as ubiquitous as I'd thought. The module should be changed
so that it can work with such crippled servers.
Status: FIXED thanks to Adam.
There is no API for deleting result sets on the server side (and
releasing associated resources in the client) except by closing the
connection through which they were created.
There is a memory leak in programs which repeatedly open and close
connections. Why isn't that handled by Perl's garbage collection?
Status: FIXED thanks to Dave.
There's no close() method for
Net::Z3950::Connections, so clients have no way to throw away
connections they've finished with.
When a fatal condition occurs on a connection (e.g. EOF), its manager
should drop its reference to that connection.
When a manager has dropped all of its connections, its wait()
method should fall out of its loop straight away, returning an
undefined value (i.e. an event happened on no connection.)
The status of each task is monitored. The possible statuses are:
(we need to fix it.)
- UNDER DISCUSSION
(perhaps because it has major implications for the
architecture, or because I don't understand what point is
being made, or because I am awaiting information from the
Z39.50 Maintenance Agency or some other third party.)
- FIXED or otherwise resolved.
Each task begins in the
state, and should eventually be progressed to FIXED. The entries
for tasks which are
may include links to separate documents summarising the discussion.
The two unresolved states are highlighted in different colours to
make it easy to recognise where work is still needed.
The following changes in status are possible: