In thread http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/7824fc19faeecc32/37e0c085d3c0ccfb?lnk=gst&q=rpc+caching#37e0c085d3c0ccfb some of you already discussed certain aspects of RPC caching.
I intend to implement caching using a Servlet Filter. However, before even getting to the difficult part I stumbled across an issue that troubles me: a sensible cache id. Usually in web app contexts you use the request path plus all the parameters to build a (unique) cache id. Hence, I tried to use the fully qualified name of the remote method being invoked. With GWT RPC calls the relevant information is "hidden" in the request content instead of parameters or attributes. The request content can only be read once from the respective input stream. The plan was to call final String payload = RPCServletUtils.readContentAsUtf8 (httpServletRequest, true); final RPCRequest rpcRequest = RPC.decodeRequest(payload, null, null); and to get the method from the request. This fails because the GWT RemoteServiceServlet also calls RPCServletUtils.readContentAsUtf8(httpServletRequest, true); which then fails because the call from my filter already loaded the request content. Any ideas around that? Marcel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
