Hi,
I guess they could improve by making these object lazy, that would provide
a better synergy between runtime performance and serialisation performance.
BigInteger and Long could keep a reference to the String representation (or
something other efficient) and just convert to the internal
Guys,
On the heels of David's post, I was going through my application and
noticed some poor RPC performance as well... much poorer than I remember. I
went through my code and noticed that I'm using Longs in every object, as
that's the default @Id for Objectify on AppEngine. Is there a simple
People,
Just to post some feedback on my problem, I actually found a working
solution and I think there is a lesson in here that it warrant me writing
back in this thread.
I managed to implement my own custom serialisation based on the flickr
post. I managed to double the performance and I
Thomas,
I just read the article on how they improved parsing time in flickr ...
really simplistic and a big surprise that the split trick is as fast as
native json parsing!
Would such an approach be usable for a generic object
serialisation/deserialisation approach ?
David
On Wednesday,
Thomas and Paul,
Thanks for all the info, I will certainly look into these alternatives.
The only problem is that somehow GWT should include a fast generic RPC
mechanism. I hate having to depend on 3rd party alternatives that are often
writen by one individual to solve his own issue and
I too am very interested in this. I absolutely do not want to jump over to
RequestFactory. I love GWT-RPC and I use it in conjunction with the Command
Pattern action/result wrapper.
I haven't seen any problems with GWT-RPC in terms of performance as I don't
currently have any high payloads
There is always RestyGWT - http://restygwt.fusesource.org/
I've been using it recently and it works very nicely in combination with
Jersey. I'm not sure on speed compared to GWT-RPC though, you'd need to
test. I haven't had any speed problems so far though.
RestyGWT will let you use raw json
Hi,
Another option is the Restlet edition for GWT:
- https://github.com/restlet/restlet-framework-java/tree/master/modules
also take a look at piriti (http://code.google.com/p/piriti/wiki/Comparison)
Cheers
Rob
Kiahu.com
--
You received this message because you are subscribed to the Google
On Wednesday, February 6, 2013 4:37:35 PM UTC+1, stuckagain wrote:
Hi,
Not sure where to ask this question, but I was wondering if the GWT devs
every plan to fix the inefficient GWT-RPC ?
The problem happens mostly on IE (all versions), although I assume other
browsers might benefit
We had similar issues with RPC especially on the iPad. In the end I wrote a
new RPC mechanism based on the command pattern that is entirely JSON based.
The client representation of server side java objects are JSO's that are
automatically maintained by a generator (outside of GWT). The RPC
10 matches
Mail list logo
