[Perlfect-search] Indexing files with automatically generated headers
Stephan Engelke firstname.lastname@example.org
Sun, 24 Sep 2000 21:58:49 +0200
On Sun, Sep 24, 2000 at 09:20:41PM +0200 wrote
Daniel Naber <email@example.com>:
> In about one month, we'll have this for Perlfect Search as well.
Great -- can't wait.
> > but as my pages contain off-site links and
> > the development system is behind a dial-up connection, indexing takes
> > forever and a day due to the timeout I have to suffer through.
> I don't understand this: You can and should use the indexer on the server
> that servers the pages. This way, it will only be a little bit slower than
> using the filesystem. No need to use http over a slow connection.
For the production system release you are right, I do run the indexer on the
server - but I like to test what I do locally *before* it goes into production.
Being behind a dialup-link means that offsite links, which are being
followed until a maximum-link-depth is reached, are not availble and will
cause the indexer to try and initiate a http-connection.
Since no such connection is possible, timeout will accour before the
indexer can continue. This is only a problem on my development system,
but it's stil annoying.
Will there be an option to stop perlfect search from following such offsite
links? Say, only follow links on a certain server which is specified in
the server config-file.
Regards -- Stephan
*** I.R.S.: We've got what it takes to take what you've got! ***