From owner-freebsd-www Fri Aug 29 03:43:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA26022 for www-outgoing; Fri, 29 Aug 1997 03:43:34 -0700 (PDT) Received: from schubert.promo.de (schubert.Promo.DE [194.45.188.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA26017; Fri, 29 Aug 1997 03:43:27 -0700 (PDT) Received: from [194.45.188.81] (stefan.Promo.DE [194.45.188.81]) by schubert.promo.de (8.8.5/8.8.5) with ESMTP id MAA12999; Fri, 29 Aug 1997 12:40:24 +0200 (MET DST) X-Sender: stefan@mail.promo.de Message-Id: In-Reply-To: <693.872848834@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 29 Aug 1997 12:42:12 +0200 To: "Jordan K. Hubbard" , jfieber@FreeBSD.ORG From: Stefan Bethke Subject: Re: Something I've always wanted to see with the mailing list search Cc: www@FreeBSD.ORG Sender: owner-freebsd-www@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 12:00 Uhr +0200 29.08.1997, Jordan K. Hubbard wrote: >Is thread preservation, e.g. when I do a search for "laptop AND IBM" >and I get my 25 hits, clicking on a given article should enable me to >travel up and down in the discussion thread with little up and down >arrows (or something) displayed along with the message. > >I mean, if my keyword search has brought me smack-dab into a juicy >thread about the exact subject I'm curious about, it stands to reason >that I'd want to read the related articles, yes? > >How hard would this be to do? I'm guessing "hard, or I'd have done >it already, eh!" as an answer. ;) > > Jordan Yes, definitly. Something like DejaNews would be nice. I just haven't found the time to do anything, but my idea is like this: To find articles fast, you need to keep an index (into the raw files). Probably by message-id. This index would also contain the basic info about an article, such as subject, author, date, thread-id. When an article is added to the index, you either look at references: or try to match the subject sensibly (there are a lot mailers that won't generate references:/in-reply-to: correctly or at all) to find the thread it belongs to. A CGI then would use the index to retrieve the message by id, and additionally show messages belonging to this thread. The thread-id could be the message-id of the first message in the thread. Decomposing (MIME-) messages needs to be done, but there is ample code one could steal (pine, mh, ...). db should suffice for the indices, although a generic (SQL-)DB would be nice. Maybe I find some time beginning of october, when I have two weeks off... Maybe, I could talk my employer into supporting this; here at Promo we could make use of this, too. I'll talk to Martin how we can at least start this; after all, we're the CGI-Joes :-) Stefan -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-0 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/