Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I recently followed this tutorial for GWT: GWT Tutorial
I am new to web development and I was telling a friend who is really good at web development that I just learned how to do an RPC call. He said that is really old fashioned and not commonly used anymore. Why would Google start out with an RPC call then? Just for simplicity? Are Restful HTTP requests the thing I should be focusing on for client/server communication?
You can club GWT with restful services and there is nothing preventing you from doing it. I know some people who have done this successfully. All the cases I know of, the RESTful service was already present/available/implemented and GWT application was supposed to be a (secondary) consumer of the service developed much later.
If you are starting fresh, it makes perfect sense to adopt the standard way of server communication in GWT – regular RPC calls. Otherwise there is no difference between REST and RPC since there is nothing you can’t do in REST that can’t be done with GWT-RPC architecture.