Local call to a service instead RPC

3 views
Skip to first unread message

Badawi

unread,
Nov 12, 2009, 8:04:57 PM11/12/09
to Google Web Toolkit
Hi,
Every call to a Service is a Remote Call?
My all application is running in the same JVM, why I have to "force"
all calls to and Remote Service and the serialize/deserialize the
object?

Is there a way to create a Asyncronous call to a Local Service?
Because if I dont need to serialize the returning object, I can use
Lazy Loading approach in my data layer.

Thanks!

Lúcio Camilo

unread,
Nov 13, 2009, 9:22:15 AM11/13/09
to google-we...@googlegroups.com
At the GWT 1.7, all of the objects have to be serialize and transit in the wire, but at the GWT 2.0 you don't need anymore, because u can use the rpc blacklist.

2009/11/12 Badawi <daniel...@gmail.com>

--

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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=.



Sripathi Krishnan

unread,
Nov 14, 2009, 7:28:08 AM11/14/09
to google-we...@googlegroups.com
My all application is running in the same JVM
I think you have the wrong idea about GWT.
GWT eventually compiles client side code into javascript. The Service call is something that the javascript code executing in browser makes to your server side code which is written in java. Hence, the concept of a Local Interface doesn't make sense at all.


--Sri


2009/11/13 Badawi <daniel...@gmail.com>
Reply all
Reply to author
Forward
0 new messages