Invoking an RPC from a locally served file (one thats loaded from file://) makes no sense. How can the filesystem possibly respond to the request in a dynamic way. The only thing it could do is try and return a file that matches the path in the RPC end point. No matter what payload accompanies the RPC the "server" in this case can only ever reply with the same precooked response. In the end this would amount to just requesting and fetching a static file, which kind of defeats the purpose of invoking a service (which tend to be "dynamic").
hyh -- 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.
