thanks for your reply raphael ... the problem i have with the "standard google's ajax crawling approach" is that I do not have a server logic, so no means to generate a servlet mapper that will spit out static versions of gwt webapp.
A friend of mine made a suggestion that the webapp should be done just in html, without any dynamics, and then enriched with the javascript (gwt). I am wondering what could be an elegant way to do such a design, avoiding any duplication of content and logic. Ideally, the content could be put in html and gwt does the voodoo ;-) -- 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/-/IBmw9RlOcXMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
