On 18 sep, 20:12, walden <[EMAIL PROTECTED]> wrote: > On Sep 18, 8:45 am, Thomas Broyer <[EMAIL PROTECTED]> wrote: > > > On 18 sep, 14:06, walden <[EMAIL PROTECTED]> wrote: > > > > Hi Thomas, > > > > Thanks for spelling that out. > > > > I do agree that GWT RPC might be less cache-friendly out of the box. > > > And that was my main point (if you're a "pragmatic developer" ;-) ) > > (along with conditional GETs which you'd have to "emulate" with GWT- > > RPC: add an ifModifiedSince parameter to all your methods and a > > lastModified timestamp to your returned objects; ...and now you're > > effectively tunneling HTTP within HTTP ;-) ) > > You take it somewhere that sounds ridiculous, while all I was getting > at was that GWT RPC might be modified slightly in order to use plain > old HTTP GET where it fits. I.e., simply specified queries where > cacheing and safety matter.
But without control on data expiration/staleness, it would be completely useless! > If there was a way to configure RPC so that the method name mapped to > a URL path and the arguments mapped to query parameters ...or eventually everything mapped to query parameters; the real need being that the request method and its arguments be serialized within the URL (the query-string fitting better with the *.gwt.xml's <servlet/ > as it's done today) > and the method > was annotated as @UseGET, and maybe some other stuff, then couldn't > this make rather good use of HTTP and reap the benefits of that? If "some other stuff" means cache directives (at the very least a max- age), then yes, that would be almost equivalent to ASP.NET's WebMethodAttribute: http://msdn.microsoft.com/netframework/system.web.services.webmethodattribute.cacheduration(VS.80).aspx It could also be something like: @CacheControl(Cacheability.PRIVATE, noStore=true) or @CacheControl(Cacheability.PUBLIC, proxyRevalidate=true, maxAge=3600) > Sure. Maybe I wasn't clear before that I'm thinking in terms of minor > enhancements to GWT RPC for these features. With some restrictions on the method arguments' types, the above should be workable as a ServiceInterfaceProxyGenerator enhancement. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
