For a finacial application ,which is not EBay or facebook i think resusing HTTP caching features has very low chances of being used since is not a common case and rarely it may happen to have that.
On Tue, Jul 7, 2009 at 3:34 PM, Thomas Broyer <[email protected]> wrote: > > > > On 7 juil, 10:18, ytrewqsm <[email protected]> wrote: > > Thx a lot...i got a lot of information...i try now to process all of > > it. > > Still after first reading ,REST like application is based on url's and > > stuff > > How can that be applied to a GWT app which is based on RPC. > > This is like a one page application....so ? > > RPC by definition isn't RESTful; but you can just use in RPC what you > learned about statelessness of the server while reading about REST; > concepts are the same, just the messages exchanged over HTTP would be > different (and make you loose ability to cache responses at the HTTP > level and otherwise control "cachingness" of your data; but if all > your data has to be requested once authenticated, this isn't a big > lost; just that you have to code a client-side cache if you want some > caching, while with a REST approach you can just take advantage of > HTTP caching features). > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
