Hi there GWT people, Please help me do my homework :-) I need to justify transitioning our web application development (which is quite peripheral from our core business) to a REST style web service + client side GWT model. Long story short, I'm pretty sure this is the most economical development model for us: We need to provide those authenticated web services anyway, and our web applications really are just that: in-browser utilities for accessing these services.
I have just one loose end: what if we suddenly need to support dumb browsers? (mobile devices, links, future stuff) I understand covering the JS-incapable segment is not a design goal of the main GWT project, and rightfully so. My patellar reaction is looking for a server side javascript container that could run the GWT client, and transfer the resulting HTML "screenshots" to the dumb browser. Everything that has onClick() becomes a link, advancing the client state in the SSJS "session", resulting in the next steady-state HTML for the browser. This is of course not universal, but for our forms-and-tables administrative applications it could work. I hope. The gwt-html approach looks nice too, but we already have JSNI code for JSON in our feasibility study pilot, so I guess we can't use that. So here are my questions: Is the above complete lunacy? What experience does the community have with executing the GWT-generated HTML+JS on the server side? Has anyone tried Jaxer, wxjavaScript, htmlUnit, Crosscheck, etc? Thanks in advance: Gabor Szokoli --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
