From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] mboxlib reloaded ;-)
Date: Sat, 28 Apr 2007 12:58:16 +0200 [thread overview]
Message-ID: <20070428105815.GB363@first.in-berlin.de> (raw)
In-Reply-To: <20070428075627.GA21610@furbychan.cocan.org>
On Sat, Apr 28, 2007 at 08:56:28AM +0100, Richard Jones wrote:
> On Sat, Apr 28, 2007 at 01:12:20AM +0200, Oliver Bandel wrote:
> > On Fri, Apr 27, 2007 at 05:29:11PM +0100, Richard Jones wrote:
> > > The source for COCANWIKI[1] contains extensive support for threading
> > > of mail messages, based on JWZ's algorithm:
> > >
> > > http://www.jwz.org/doc/threading.html
> >
> > Nice... you speak of an optimized algorithm for threading.
> > I didn't explored your solution nor did I explored your
> > paper in detail (tomorrow I think I have the time to do it),
>
> I should point out that the algorithm is due to esteemed hacker[1]
> Jamie Zawinski (http://jwz.org) who used it in Netscape versions 1
> through 3. They got C++/OO group-think disease from Netscape 4 and
> above (the rot continues to this day).
When I think about netscape, I think about the terrible way,
how it handles newsgroups....
...when doing a resort of the newsgroup-entries it's extremely slow.
Maybe it again checks data on the newsserver again and again.
And when I think about Netscape, I se that it reloads data via network,
when you want to save it, even if it' already on the screen.
So, theese things are the reason, why I don't see why this algorithm
is something special, until I have seen that it really is fast. ;-)
I have thought a while about the threading, and thought I have some good ideas.
A while later, I saw, there already is a datastructure that is useful
for threading, and it is the Tries-datastructure:
http://www.csse.monash.edu.au/~lloyd/tildeAlgDS/Tree/Trie/
If you use the message ID's instead of the char's of a word,
then this datastructure is well suited for news-/mail-threading, I think.
So, other people already had done, what can be used here.
But maybe thze algorithm you show on your pages is really good.
But I would trust your algorithms more than algorithms of
netscape-programmers ;-)
But maybe it's really good and only the overall-design of Netscape was bad. ;-)
Ciao,
Oliver
next prev parent reply other threads:[~2007-04-28 10:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 13:54 Oliver Bandel
2007-04-27 16:29 ` [Caml-list] " Richard Jones
2007-04-27 23:12 ` Oliver Bandel
2007-04-28 0:54 ` skaller
2007-04-28 10:47 ` Oliver Bandel
2007-04-28 10:54 ` Gabriel Kerneis
2007-04-28 11:44 ` Oliver Bandel
2007-04-28 13:49 ` skaller
2007-04-28 14:18 ` Oliver Bandel
2007-04-29 10:45 ` Richard Jones
2007-04-29 15:41 ` Oliver Bandel
2007-04-29 18:51 ` Robert Roessler
2007-05-01 11:00 ` camomile-problem (Re: [Caml-list] mboxlib reloaded ;-)) Oliver Bandel
2007-05-01 10:56 ` [Caml-list] mboxlib reloaded ;-) Oliver Bandel
2007-04-28 7:56 ` Richard Jones
2007-04-28 10:58 ` Oliver Bandel [this message]
[not found] ` <20070429103911.GA30510@furbychan.cocan.org>
2007-04-29 15:43 ` Oliver Bandel
2007-09-24 18:22 ` ocamllex speed [was Re: [Caml-list] mboxlib reloaded ;-)] Bruno De Fraine
2007-09-24 19:54 ` Alain Frisch
2007-09-25 8:53 ` Bruno De Fraine
2007-09-24 22:06 ` skaller
2007-09-27 5:26 ` Chris King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070428105815.GB363@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox