Thanks Karthik for the reply. Client side rendering (DOM manipulation) and Server side rendering (HTML manipulation), certainly these achieve rendering efficiency, but still programming approach is still same, that client side event programming.
Server can get away from rendering totally, keeping the business logic with it, and serve view+model+presenter to server, so that client can what it is best at, and server can what is best at. Creating event is the only way to get any resource from server in current GWT during run time. Please correct me , if wrong. Server could send entire page + presenter as as java script and Model to client, We can leverage Browser DOM, to apply Model to view as in today. That way you only serve the java script, really you need. Programmer can only visualize the page is in AJAX world, I have seen extreme apps, there is only single page, other extreme our jsp page with little java script. Code splitting, server rendering - makes different. But approach remains same, where client will have entire app and makes server calls on user events. We can get the best of both worlds, like every thing on server (jsp model) and every thing on client (GWT) model. Server should remain as brain for using Enterprise resources etc, that server will be able every thing that is need for client, for ajax page in one shot, Client can do DOM manipulation, little bit of event-ing if required, like refreshing with new values etc. Hand written AJAX page should be same as GWT generated page, that GWT will remain like tool, still programmer will have flexibility to choose what approach suits for his application. For few web apps, RIA approach may be more lively. Is there any easy way in GWT, to post entire page and get new page ? On Aug 6, 6:33 pm, Karthik Reddy <[email protected]> wrote: > Or you could wait for server-side rendering to be supported by GWT. The GWT > team has dropped few hints in a couple of threads indicating that the day > could not be very far off when GWT does support server-side rendering. See > the following threads: > > https://groups.google.com/forum/#!topic/google-web-toolkit-contributo... > * > ...............It allows us to optimize for different browsers, and it even > opens the door for server side rendering. > > * > * > * > *https://groups.google.com/forum/#!topic/google-web-toolkit-contributo... > * > *The latter can be user in a regular JVM to create an HTML string, which > will hopefully help with server side rendering in the future. > * > * > * > Another relevant thread I have started regarding GWT, Closure, server-side > rendering* : > *https://groups.google.com/forum/#!topic/google-web-toolkit-contributo... -- 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.
