From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [Heliotrope] why whistlepig?
Date: Fri, 24 Feb 2012 22:39:50 -0800 [thread overview]
Message-ID: <1330151741-turnsole-57719@terminus-est> (raw)
In-Reply-To: <20120224051907.5668.78469@localhost>
Excerpts from Serge Z's message of 2012-02-23 21:19:07 -0800:
> Why not xapian?
At least as of a year ago when I looked at Xapian, the incremental
indexing was painful (you had to keep a separate smaller corpus of
additions, reindex it every time a new document was added, and merge
when it got too big), doing anything outside of indexing MySQL rows was
extremely painful (you had to use some weird XML format that I could
never get quite right), and there was no way to have mutable arbitrary
labels.
I also prefer to keep everything in a single process, but that's
not a hard requirement.
--
William <wmorgan@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2012-02-25 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 5:19 Serge Z
2012-02-25 6:39 ` William Morgan [this message]
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=1330151741-turnsole-57719@terminus-est \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.org \
/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