Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 74540 invoked from network); 14 Jan 2000 12:34:19 -0000 Received: from anchor-post-32.mail.demon.net (194.217.242.90) by 63.211.145.10 with SMTP; 14 Jan 2000 12:34:19 -0000 Received: from media.demon.co.uk ([158.152.20.147] helo=192.168.0.2) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 1295tX-0008Wr-0W for cocoon-dev@xml.apache.org; Fri, 14 Jan 2000 12:32:00 +0000 Date: Fri, 14 Jan 2000 11:24:44 +0000 From: Jeremy Quinn Subject: Re: search engine To: cocoon-dev@xml.apache.org X-Priority: 3 In-Reply-To: <387E8058.BAAFF572@apache.org> MIME-Version: 1.0 Content-Type: text/plain; Charset=US-ASCII X-Mailer: Mailsmith 1.1.4 (Bluto) Message-Id: On 13/1/00 at 5:48 pm, pier@apache.org (Pierpaolo Fumagalli) wrote: >Jerm wrote: >> With an XML list of your site's files to play with, it could be possible to >> make an XSL that acts as a basic search engine for your site with Cocoon, >> using the document() function; >But I think it would be so slow... Being orthogonal to HTML, also, an >XML search engine should be able to work on different data, like, since >most of the DTDs are "site specific", working on the contexts where >keywords to search are found (If I look for a product called "FOOBAR" on >my site, the search engine might be "clever" enough to search the word >"foobar" in the tag...) I agree! Very slow, and have to be built specially for each DTD. But while another solution does not exist (?) it could be a temporary solution. regards Jeremy ____________________________________________________________________ Jeremy Quinn media.demon webSpace Design