[KinoSearch] Setting up search server and client

Dan dmarkham at gmail.com
Tue Nov 9 01:43:29 PST 2010

Hello Paweł,

I'm not 100% sure I understand what your asking but I'm going to try and
help ya anyway.

The SearchServer and SearchClient I would say are fully working samples of
one way to use KinoSearch in a client / server model.

It might not be the best/fastest way to access a Kino index depending on
your needs.

If you have not done so yet i would play with the sample scripts (
indexer.pl/search.pl)  just to get a feel.

As for the caching..
KinoSearch doesn't do search result caching on it's own (you would need to
cache in memcached/etc.)

What it does do is work with your operating system's VM/disk cache to keep
the index fast for all your searches.

Depending on your index size / querys you may not need caching at all.

Good luck,

2010/11/8 Paweł Matykiewicz <pawel.matykiewicz at gmail.com>

> I assume that SearchServer is faster than mod_perl. Are there any
> extra guidelines how to setup SearchServer and SearchClient (not
> included in CPAN web-site)? I'm used to PubMed Entrez API which
> requires a history token for retrieving search results. So my question
> is if I need to do anything extra in KinoSearch to cache search
> results for each user? Let's say in one request I want to know the
> number of results then close all connections and later get a subset of
> document IDs, etc.
> Thank you
> Regards
> --
> Pawel Matykiewicz
> http://www.neuron.m4u.pl
> http://www.linkedin.com/in/pawelmatykiewicz
> _______________________________________________
> kinosearch mailing list
> kinosearch at rectangular.com
> http://rectangular.com/cgi-bin/mailman/listinfo/kinosearch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rectangular.com/pipermail/kinosearch/attachments/20101109/5a647e8c/attachment.html 

More information about the kinosearch mailing list