At 03:19 PM 07/30/01 -0400, Rocco Caputo wrote:
>P::W::Run does the usual pipe/fork/exec for stand-alone programs. It
>also can execute functions in child processes with the usual stdio
>pipes back to the parent.
>
>In this model, the main process acts as a proxy between clients and
>the back-end processes. That's extra overhead you may not want.
Because of performance reasons?
>> Any suggestions?
>
>Build your dream design on paper, ignore system requirements and
>limitations at first, and then find work-arounds or implementations
>for the sci-fi stuff until it's feasable. :)
That's a good idea. I'm not sure I'm familiar enough with different
designs to pick the best. Apache is a model I'm somewhat familiar with,
which is what I though of that.
>Does SWISH-E load the entire index file into memory? The interface
>seems to follow a pattern where data is iterated over on disk, but my
>first exposure to it was just a few minutes ago.
Right. When the index is first opened it reads header info, and reads in
some hash value-to-seek position tables at startup. This is the operation
that could be done once at server startup.
And there's also a version in development that uses Berkeley DB as a
backend (to allow incremental indexing).
Bill Moseley
mailto:[EMAIL PROTECTED]
