I second the opinion that proper full text search should have been in the road map. My app soon will need fulltext searching. I'm considering dumping all the data in google base and "forwarding" the searching against the google base api. I wonder if I'd be violating google base terms of service or whether there is a cap on queries, etc. Haven't checked.
Anyhow, from my perspective, the priorities are also dead wrong, unless the current aim has shifted to get corporations to start outsourcing some of their stuff to the cloud. Hence java support. I'm happy, though, about the "cron", it might come in handy for the dumping business (not without irony) Google: The (albeit monumental) task of changing the rules of the game for web startups won't be completed until full text is available. On Apr 9, 7:41 pm, dalenewman <dalenew...@gmail.com> wrote: > I concur also. > > I expected to see "Search API" right next to "Datastore API" when I > started working with GAE. > > It makes sense and fits the model; offer some for free and then charge > for more. > > I would think a Search API that leveraged Google's search > infrastructure would be GAE's killer app. > > However, maybe with java support now, you can run Lucene. I imagine > there might be some problems writing the indexes to the filesystem > though, which is really why you'd need search to be an infrastructure > aware API like datastore or memcache. > > Dalewww.bookdope.com --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
