GWT is for "apps" — right? But what's about static pages? (GWT's Future Plans...)

GWT is a framework for building Ajax apps that act as clients and (optionally) communicate with a kinda RESTful backend via RPC or using RequestFactory (both are JSON based). That's my to the point understanding of GWT.

But what's about static pages? To deliver static content, especially for search engines and other crawlers GWT might be not the best choice (yet?) because the whole GWT app is located in a single JS file and other subsequently fetched files. Those crawlers need static snapshots of a certain page state. In fact there are approaches and proposals to make Ajax apps crawlable. This is a a general proposal from Google of how to make an Ajax page crawlable. And Acris is a GWT-based framework that implements Google's proposal (haven't tried it, don't know how good it is). 

However both approaches are everything else but straightforward or even fast&easy to apply to already existing Ajax/GWT apps. So my question is primarily directed to GWT core devs: Are there plans to implement an easy-to-use "static snapshot of a certain Ajax state" feature into GWT? Or is this a problem domain that will never be addressed by GWT?

The problem arises from the fact that a company cannot rely on GWT only if it wants to maintain a SEO-friendly and crawlable content-driven page. For this purpose Wicket, Tapestry and other Java frameworks have to be used.

-Alex

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/WYxEBCRpKjUJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.