Suchmaschine clientseitig???

[Guido Bayer]

Hallo,

ich bin auf der Suche nach einer Möglichkeit, clientseitig eine Suchmaschine für die Abbildung einer Datenbank zu haben (ne Menge Tabellen halt) zu bauen.

Das ganze soll dann per Browser von einer CD-ROM aus lauffähig sein (ohne Installation, also nix PHP leider...).

Mit JavaScript habe ich da eine Lösung bei Oreilly gefunden(www.oreilly.com/catalog/jscook/chapter/ch01.html), die aber anscheinend nur begrent leistungsfähig ist (wird wackelig ab etwa 6000 Datensätzen).

Allerdings ist der Artikel von 1999, vielleicht gibt's da ja inzwischen bessere Algorithmen oder auch ganz andere Lösungen.

Für alle Ideen, Tipps, Ansätze und Kommentare dankbar,

Gruss,

Guido bayer

[Alexander Foken]

Moin Moin !

"Mein" Perl Bookshelf benutzt eine lizensierte, Java-basierende Suche namens "NetResults":

About Searching this CD

This CD includes search technology from Astaware technologies Inc http://www.netresults-search.com/. Your Web browser uses an ordinary HTML form like this one to perform the search by communicating with a single-purpose Web server, written in Java.

Therefore, in order to search the CD, the search server must be running. In order for the search server to run, you must have a Java interpreter, either the Java Developers' Kit (JDK) or the Java Runtime Engine (JRE). A JRE is provided for some platforms on this CD; you may already have the JDK installed as part of your operating system. If you haven't run the server before, or if you're having difficulty, please see below.

The search engine supports basic Boolean operators: AND, OR, and NOT. You can use these to refine your search. Example:

pipe AND stderr NOT stdout

You can use an asterisk (*) as a wildcard operator:

bob*
will match "Bob", "bobwhite", and "bobsled".
*bob
will match "Bob", "kabob", and "nabob".
*bob*
will match "Bob", "bobsled", "kabob", and "discombobulate".

The Results report format setting controls the style of report received. A Simple report will just list the documents found and a relevancy ranking; an Expanded report will give the first section of the document's content.

The search engine does not search for punctuation; it only indexes words of letters and numbers. For example, to find <STDIN>, search for STDIN or stdin (case does not matter). Note that there is an index available which indexes symbols and keywords; this can also be useful for finding concepts whose names do not necessarily appear literally in the text of a book.

Some punctuation can be used as shortcuts for Boolean keywords:

&
AND
|
OR
!
NOT

The example search above can therefore be entered as

pipe & stderr ! stdout

If you use any of these characters in a context where the search engine does not understand them, you will get an "Invalid response" error message. Correct the syntax of your search expression and try again.

Alexander