Hmmm, your right. You could try culling some of the token words, the simple ones like 'and', 'a', 'or' to limit the number of puts, but that will only go so far.
I don't think sorting and checking for intersection will cost you too much. Its the number of results returned from the queries that chew up the CPU cycles. Slicing/pagination doesn't really seem worthwhile if you've got all the results (which would occur if you used this approach). I'm out of ideas, would be interested to know if you do find a solution though. It sounds like something a lot of apps would need to do. Good luck ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
