|
From: Geoff H. <ghu...@us...> - 2002-12-29 08:13:49
|
STATUS of ht://Dig branch 3-2-x
RELEASES:
3.2.0b5: Next release, tentatively 1 Dec 2002.
3.2.0b4: "In progress" -- snapshots called "3.2.0b4" until prerelease.
3.2.0b3: Released: 22 Feb 2001.
3.2.0b2: Released: 11 Apr 2000.
3.2.0b1: Released: 4 Feb 2000.
(Please note that everything added here should have a tracker PR# so
we can be sure they're fixed. Geoff is currently trying add PR#s for
what's currently here.)
SHOWSTOPPERS:
* Mifluz database errors are a severe problem (PR#428295)
-- Does Neal's new zlib patch solve this for now?
KNOWN BUGS:
* Odd behavior with $(MODIFIED) and scores not working with
wordlist_compress set but work fine without wordlist_compress.
(the date is definitely stored correctly, even with compression on
so this must be some sort of weird htsearch bug) PR#618737.
* Not all htsearch input parameters are handled properly: PR#405278. Use a
consistant mapping of input -> config -> template for all inputs where
it makes sense to do so (everything but "config" and "words"?).
* META descriptions are somehow added to the database as FLAG_TITLE,
not FLAG_DESCRIPTION. (PR#618738)
PENDING PATCHES (available but need work):
* Additional support for Win32.
* Memory improvements to htmerge. (Backed out b/c htword API changed.)
* Mifluz merge.
NEEDED FEATURES:
* Field-restricted searching. (e.g. PR#460833)
* Return all URLs. (PR#618743)
* Handle noindex_start & noindex_end as string lists.
* Quim's new htsearch/qtest query parser framework.
* File/Database locking. PR#405764.
TESTING:
* httools programs:
(htload a test file, check a few characteristics, htdump and compare)
* Turn on URL parser test as part of test suite.
* htsearch phrase support tests
* Tests for new config file parser
* Duplicate document detection while indexing
* Major revisions to ExternalParser.cc, including fork/exec instead of popen,
argument handling for parser/converter, allowing binary output from an
external converter.
* ExternalTransport needs testing of changes similar to ExternalParser.
DOCUMENTATION:
* List of supported platforms/compilers is ancient. (PR#405279)
* Add thorough documentation on htsearch restrict/exclude behavior
(including '|' and regex).
* Document all of htsearch's mappings of input parameters to config attributes
to template variables. (Relates to PR#405278.)
Should we make sure these config attributes are all documented in
defaults.cc, even if they're only set by input parameters and never
in the config file?
* Split attrs.html into categories for faster loading.
* Turn defaults.cc into an XML file for generating documentation and
defaults.cc.
* require.html is not updated to list new features and disk space
requirements of 3.2.x (e.g. phrase searching, regex matching,
external parsers and transport methods, database compression.)
PRs# 405280 #405281.
* TODO.html has not been updated for current TODO list and
completions.
* Htfuzzy could use more documentation on what each fuzzy algorithm
does. PR#405714.
* Document the list of all installed files and default
locations. PR#405715.
OTHER ISSUES:
* Can htsearch actually search while an index is being created?
* The code needs a security audit, esp. htsearch. PR#405765.
|
|
From: Brian W. <bw...@st...> - 2003-01-13 04:48:22
|
>... >NEEDED FEATURES: >... >* File/Database locking. PR#405764. Can you tell me a little more about this - I had started working on a generalized file locking mechanism as part of my Adjustable Logging patch, implemented using a "factory" method to create objects to an interface I might be able to do this one. Regs Brian ------------------------- Brian White Step Two Designs Pty Ltd Knowledge Management Consultancy, SGML & XML Phone: +612-93197901 Web: http://www.steptwo.com.au/ Email: bw...@st... Content Management Requirements Toolkit 112 CMS requirements, ready to cut-and-paste |
|
From: Geoff H. <ghu...@ws...> - 2003-01-16 16:27:10
|
>> * File/Database locking. PR#405764. > > Can you tell me a little more about this - I had started > working on a generalized file locking mechanism as part > of my Adjustable Logging patch, implemented using a > "factory" method to create objects to an interface I don't know about a "factory" method. But the item hasn't changed in any substantial way since the previous discussion of locking (which looks like Sep-2002). http://sourceforge.net/mailarchive/message.php?msg_id=2014435 -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ |
|
From: J. op d. B. <ht...@op...> - 2003-01-20 12:13:00
|
Basicly there are three methods: flock() (on some versions of *nix) lockf() (on other versions, like HP-UX) ioctl() (on yet other versions), So we need to find what versions are supported. Some implementations can only lock a whole file, some can lock parts of a file. Geoff Hutchison wrote: >>> * File/Database locking. PR#405764. >> >> >> Can you tell me a little more about this - I had started >> working on a generalized file locking mechanism as part >> of my Adjustable Logging patch, implemented using a >> "factory" method to create objects to an interface > > > I don't know about a "factory" method. > But the item hasn't changed in any substantial way since the previous > discussion of locking (which looks like Sep-2002). > > http://sourceforge.net/mailarchive/message.php?msg_id=2014435 > > -- > -Geoff Hutchison > Williams Students Online > http://wso.williams.edu/ --Jesse |