I don't know exactly how many characters the search string can have, but to pare it down, the first thing I would do is figure out a way to eliminate the markup, newlines (i.e., line breaks) and stop words (i.e., words that Google won't search for anyway, like a, an, the, in, etc.) from your query. This will save you characters that would otherwise be wasted anyway, and possibly a little time sending/ receiving your query. As far as search operators (e.g., pipes, parentheses, AND, OR, etc.), I think I remember seeing somewhere that you *should* be able to use anything you can in a regular Google query.
And re: your additional inquiry (i.e., rolling your own Google), I think you'll find that a challenge for two reasons. While it's not particularly difficult to build a spider that would parse the pages into keywords, etc., Google is very tight-lipped about the algorithms it uses to weight or order its results. Jeremy R. Geerdes Effective website design & development Des Moines, IA For more information or a project quote: http://jgeerdes.home.mchsi.com [EMAIL PROTECTED] If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google AJAX API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-AJAX-Search-API?hl=en -~----------~----~----~----~------~----~------~--~---
