Hi there, are there any chances to get stable .rpc files in upcoming releases? I remember that the images generated by imagebundle had stable filenames across compiles, somehow dependent from images hashcode.
I have seen comments here and there praising "rest" or "autobeans+requestbuilder", but neither one of the approaches provide polymorphism and as far as I know both would have troubles with object cycles. IMHO, rest or auto beans are wrong for client-server on so many levels that I stopped counting. I am expecting a flame war on this statement, but I am very convinced that none of them do really solve issues I have in client-server communication in product development. I am using the command pattern and very happy to have with multiple versions, batching, recording, reuse, central exception handling, etc. I have a plain pojo communication model, and gwt-rpc simply gets things done pretty well. Unfortunately, the .rpc files are not stable - and they are the last mile for me to have real zero downtime deployments. I even do export my dispatch service as httpinvoker/ exporter and can reuse the same communication layer for pure java clients. I have a proprietary http/json converter in a servlet for my iOS app. But this is another story and does not have the issues I have on the GWT side with the .rpc files. I am willing to switch at any moment, all I need is a GWT-RPC replacement that handles <R extends Result> R execute(Action<R> action) throws DispatchException; properly. It would take me no time to change, all communication runs over pojis/ pojos. Any suggestions? brgds, Papick -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
