Ok fine Mike..
Any way i observed that from programmer perspective usage of RPC saves
from lot of burden( i mean data transfer exchange)
Thank you Mike
On Aug 19, 11:57 am, mdwarne mike.wa...@gmail.com wrote:
Hi venkl,
We use RPC because it makes things so simple.
For some of our service
Ok i got the point. Thank you dave
On Aug 20, 2:31 am, DaveS dave.sell...@gmail.com wrote:
I don't think you're ever *forced* to use RPC, it simply requires
writing a lot less code than writing a servlet, parsing XML, returning
XML and parsing that result in the client. GWT makes it very
I don't think you're ever *forced* to use RPC, it simply requires
writing a lot less code than writing a servlet, parsing XML, returning
XML and parsing that result in the client. GWT makes it very easy to
use RPC, but doesn't force you to do so.
In our app we do both, but by far the majority of
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
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
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
