You can probably generate the page against production data and store it in a static directory. I just looked at this sample code:
http://code.google.com/web/ajaxcrawling/docs/html-snapshot.html <http://code.google.com/web/ajaxcrawling/docs/html-snapshot.html>My intuition says most of this can probably be done with URLFetch and possibly Rhino (this is what HtmlUnit uses under the hood), though I'm not familiar with using Rhino with DOM manipulation. On Wed, Mar 24, 2010 at 3:43 PM, Peter Warren <[email protected]>wrote: > I have a Google Web Toolkit client that is served from Google App > Engine. I'm trying to follow the Google-recommended practice for seo/ > crawling of ajax apps outlined here: > http://code.google.com/web/ajaxcrawling/. > > 1) I understand that HtmlUnit doesn't work on App Engine. Is that > right? > > 2) Are there any other headless browser APIs that would work on App > Engine, or any other alternatives for serving html snapshots of my > application? > > Thanks, > Peter > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en.
