Greets,
This is a form letter I copy and paste into replies when I receive
emails regarding KinoSearch that I think might be appropriate for the
public mailing list.
I get a lot of private correspondence regarding my multiple CPAN
distributions: bug reports, design suggestions, feature requests,
support requests, full blown patches, replies accidentally sent to me
rather than the list (did you hit "reply" or "reply all"?), even
thank you notes. :) In most cases, it is better that KinoSearch-
related discussions take place in a public forum.
* More brains available for storming.
* Other people may benefit from seeing what you wrote.
* A public archive is created.
I don't hesitate to send this letter out, even when I have previously
communicated with the recipient. I ask you to understand that
although I appear to write fairly well, it's a slow and laborious
process -- I'm a lousy writer but a decent editor, and I get
acceptable results only by refining multiple drafts, even with
email. Since I invest so much energy in each piece of written
correspondence, I need to maximize the return on my investment, which
is why I aggressively shunt as much traffic as I can onto the public
lists, and also why I don't personalize this form letter. :)
If you're not already subscribed, information regarding the
KinoSearch mailing list can be found at <
http://www.rectangular.com/
mailman/listinfo/kinosearch/>.
Thanks for writing,
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
On Feb 23, 2006, at 6:16 PM, javacocoon@gmail.com via RT wrote:
Show quoted text>
> <URL:
http://rt.cpan.org/Ticket/Display.html?id=17833 >
>
> Hi Marvin -
> Thanks for the explanation. Makes sense.
>
> I am planning to use this on a large, mostly html files based site.
> I understand about the disclaimers. Couple of questions
>
> 1. Are you aware of any security tests done on this module ?
> 2. Any performance stats ?
>
> Appreciate your opinion.
>
> Thanks
> srini
>
>
> On 2/23/06, marvin@rectangular.com via RT <bug-
> KinoSearch@rt.cpan.org> wrote:
>> In your particular case, index.html is not getting picked up because
>> invindexer.plx is specifically set up to ignore a file with that
>> name, so no docs are being added (remove the "next if" line to fix
>> the problem). KinoSearch isn't set up yet to handle that situation
>> yet, and is producing a misleading error message. I'll add code in
>> the next release so that InvIndexer just writes an empty invindex
>> without complaint if you don't ever add_doc.
>>
>> Marvin Humphrey
>>
>>
>
>