[KinoSearch] serializing safely

[Hans Dieter Pearcey]

I'm going to be using KS in a persistent environment (a fastcgi).  The
Searcher/IndexReader docs recommend caching the searcher for better
performance.

Because my fastcgi (as so many others) has multiple children, my first instinct
is to store the searcher in the session so that any of the children can get at
it as needed.  I know that a bunch of the KS guts are XS or C, though; what
things can be safely Storabled and put into a database, and what things will
either blow up or silently not work?

hdp.