I am just wondering it.Anybody has practical experience on this?
--
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
Hi,
I have working app with internal GWT serialization, e.g. works via RPC. Now
I want to expose server side functionality as RESTful service for other type
of clients (not only GWT). I see that now I have to make some explicit JSON
serialization. What is the less painfull way to do that? Some
code.google.com/p/google-gson
flexjson.sourceforge.net
On Apr 2, 5:51 am, Alexander Krasnukhin the.malk...@gmail.com wrote:
Hi,
I have working app with internal GWT serialization, e.g. works via RPC. Now
I want to expose server side functionality as RESTful service for other type
of clients
I don't know if this will help you, but you can still use JSON with
GWT-RPC. What I do is use GSON which is another Google API for
converting Java objects to a JSON string. Once you have the JSON
string you can easily parse it using GWT's JSON capabilities.
You can get more information from here
I will probably write up a summary of my experience with this, but my
application just switched from using JSON to RPC as the payload for
the initial data set embedded in the original HTML sent from the
server on the first request. We've also been slowly converting our
JSON HTTP requests to RPC
I haven't touched gwt rpc, as it just seems using requestbuilder and
shoving json across the wire is straightforward.
What's the compelling case to use gwt rpc? Remember, I haven't even
looked at the docs. I'm not trying to bash anything here, just
wondering why it's worth it to setup gwt rpc vs
.
- There's plans to make the deserialization of RPC responses
asynchronous so you don't tie up the browser thread reading large
responses. You'd have to do the same thing manually with large JSON
responses.
- Using RPC is a nice way of abstracting the transmission details and
saying I don't care about
Sounds pretty good. Seems like I spend half my time typing:
int n = (int) jsonNum.isNumber().doubleValue();
String s = jsonStr.isString().stringValue();
...
Just calling a method that demarshales to the correct type would be
nice. Not sure it's worth my perceived pain of switching and pinning
don't tie up the browser thread reading large
responses. You'd have to do the same thing manually with large JSON
responses.
- Using RPC is a nice way of abstracting the transmission details and
saying I don't care about the wire format of your requests and
responses. This means client
JSON
responses.
- Using RPC is a nice way of abstracting the transmission details and
saying I don't care about the wire format of your requests and
responses. This means client-server interface management is reduced
to managing the evolution of a Java interface, rather than worrying
about
if your JSON is coming from a trusted source, you really should have a
look at overlay types in GWT. It is much simpler (and faster) than
mucking about with the JSON parser.
-jason
On Oct 29, 2008, at 8:31 AM, Brian wrote:
Sounds pretty good. Seems like I spend half my time typing:
int n
The current RPC wire format is asymetric, meaning that the same object
going to the server will look different than coming from the server.
There also isn't really a published spec for the RPC wire format as it
tends to change from version to version of GWT.
In GWT, this is not an issue
the deserialization of RPC responses
asynchronous so you don't tie up the browser thread reading large
responses. You'd have to do the same thing manually with large JSON
responses.
- Using RPC is a nice way of abstracting the transmission details and
saying I don't care about the wire
Thanks for the info. Yeah, I've got all the biz logic broken out from
the protocol, as I support form post and json get's using the same api
(essentially...) It's interesting that the wireformat is json. I was
sorta hoping it was some super tight binary format that would tempt me
to switch (I'm
Iam confusing which one i need to use to get data from server.. JSON
object or GWT RPC calls.
.Can somebody tell me the advantage and disadvantage of both?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web
If your server is written in Java, it will be easier and more efficient to
use GWT RPC. If it's in Python or something else, you may have to use JSON,
though there is some code
http://code.google.com/p/python-gwt-rpc/%20available to help you do
RPC from a GWT front end to a Python-based App
Hi there
I'm with Isaac on this one! I have written both GWT RPC callbacks and
JSON types of communication.
We use purely java so I have had experience with both in a Java
container.
If your application will only reside on your server so no Cross Site
Scripting issues I'd really go with GWT
, 2:45 am, eggsy84 [EMAIL PROTECTED] wrote:
Hi there
I'm with Isaac on this one! I have written both GWT RPC callbacks and
JSON types of communication.
We use purely java so I have had experience with both in a Java
container.
If your application will only reside on your server so no Cross
as well.
Later,
Shaffer
On Oct 17, 2:45 am, eggsy84 [EMAIL PROTECTED] wrote:
Hi there
I'm with Isaac on this one! I have written both GWT RPC callbacks and
JSON types of communication.
We use purely java so I have had experience with both in a Java
container.
If your
19 matches
Mail list logo
