Hi venkl, We use RPC because it makes things so simple. For some of our service calls we pass java objects as parameters to the service.
The response coming back are also java objects. such as lists and arrays of data etc. Boolean, integers, dates etc are automatically converted, and arrive in their native format on either side (client or server). RPC will automatically convert the java object, and escape any funny characters and send the objects back and forth from client to server etc. If you don't use RPC, then you as the Programmer, will be responsible for creating your own messages, and parsing them. You will also need to make sure you encode/decode any special HTTP reserved characters. RPC is great if you are comfortable using a Java Servlet on the server. If you want to use PHP, or other types of services, then you must use JSON, or XML etc to pass your data back an forth, unless the response is simple text. Mike. On Aug 19, 2:43 am, venki <pola.ve...@gmail.com> wrote: > Thank you DaveS > > Ok cool instance... One more doubt Dave. I understand your example. > Let us suppose my service is going to use by GWT client only. So in > this case i can use either GWT RPC or HTTP. So i can do my application > with out using RPC also rather i can use HTTP.Can you please tell me > an instances why should i opt for GWT RPC mechanism only. I mean i am > expecting the answers that in what cases we are forced to use RPC > rather than HTTP. If possible can you please tell me the advantages > RPC over HTTP. > > Once again thank you very much for your reply.. > > Have a good day Dave > > On Aug 19, 1:34 pm, DaveS <dave.sell...@gmail.com> wrote: > > > > > Our application uses both, depending on quite a few factors. In some > > cases we are putting data into Flash (.swf) components, and need it in > > XML, so we use a 'raw' HTTP request to get the data. In most other > > cases we use GWT RPC to retreive data from the server, or to initiate > > actions in the server. There really is no single answer, it just > > depends on your application. > > > We have considered moving away from GWT RPC more than once, thinking > > we might provide an 'open interface' or web-service interface, but so > > far the convenience of RPC has been the overwhelming reason we are > > continuing to use it. > > > I guess you could say, if there is no need to make the service > > available to anything other than your GWT client, then use RPC, but if > > you want to open the interface to 3rd parties, other apps or anything > > like that, consider using HTTP. > > > Dave. > > > On Aug 18, 5:56 pm, venki <pola.ve...@gmail.com> wrote: > > > > Hi to all, > > > > I am new to GWT. I read GWT communication with server tutorial. It > > > provides various mechanisms to communicate with the server. Any way i > > > know how to use GWT RPC and HTTP mechanism to communicate with > > > server. > > > > I request all of you can you give perfect explanation towhenshould > > > we use RPC mechanism andwhenshould we use HTTP mechanism. I mean at > > > what type instances we are forced to use particular mechanism. > > > > Great thanks in advance.. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
