Hi Mohammed. If you're looking for a replacement for RequestBuilder, which is a low-level approach for requesting, with all its flexibility, you would better go with a high level http client api.
To fulfill exactly this need, I developed Requestor <https://github.com/reinert/requestor>, which is really an HTTP Client API for GWT. I strongly recommend you to try it, since it offers everything you need to communicate via HTTP out of the box and many other features for a good HTTP Client API. (I've modeled it based on successful APIs from the Python, JS and Java communities) You won't need to worry about json serialization (many alternatives are available for it), binary data manipulation, authentication, and many other things. The API has a very elegant idiom and you find it simple and intuitive to make requests (a comparison with RequestBuilder is shown at the project home). Cheers. Em segunda-feira, 9 de fevereiro de 2015 09:41:03 UTC-3, Mohammed Sameen escreveu: > > Hi, > I created big application using GWT and am using RequestBuilder to > communicate with the server.So what is the best way for communicate to > server from client. > i)RequestBuilder > ii)GWT RPC > iii)Any other approach(GWT Errai). > > > I came to know that using GWT RPC is huge pain , so,what are the drawback > of using GWT RPC?what is the best approach?Please give me suggestion? > -- 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.
