--On Friday, August 16, 2002 9:54 PM -0700 Chuq Von Rospach
<chuqui@plaidworks.com> wrote:
> On 8/16/02 9:31 PM, "Tom Neff" <tneff@grassyhill.net> wrote:
>> The meta-lesson, if you will, is that you should store your list archives
>> in the most presentation-independent format possible, so as to preserve
>> your options when you change your mind every five years, or when archive
>> browsing technology leaps. Don't cook messages permanently into HTML
>> pages.
>
> That's exactly what germinated this idea. USENET fails to scale because it
> sends every byte every where in case anyone anywhere might want it.
Actually, Usenet (I still remember the capswars on that one) scales well
because as long as Google Groups grabs the posting, you can search from
there forever. In the here and now, Usenet's biggest problem is that
specialty groups lack distribution, i.e., it DOESN'T send every byte
everywhere in general, it only sends what servers are configured to get.
> So what I decided to explore was to simply (hah!) dump everything into
> MySQL, use MySQL's fulltext search system as the basis of a search
engine...
I think that I would be as terrified of entrusting a list's long-term
archive to MySQL as any other possible software choice. Plain text would
rule for me.
Follow-Ups:
References:
|
|