Stack overflow
posted 15 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
I am encountering a "Stack overflow at line: 0" message
upon receiving the result of an RPC invocation.
I have this problem in gwt-2.0.3 in IE 6.(not in Mozilla)
i am calling RPC call. in return it returns huge amount of data. containing many lists, hash-sets. is this problem is due to this RPC call.
what should i do to resolve this problem??
also some time i got message than internet explore to run slow because of this script..
check the attachments...
refer
Google Issue 1438
also.
upon receiving the result of an RPC invocation.
I have this problem in gwt-2.0.3 in IE 6.(not in Mozilla)
i am calling RPC call. in return it returns huge amount of data. containing many lists, hash-sets. is this problem is due to this RPC call.
what should i do to resolve this problem??
also some time i got message than internet explore to run slow because of this script..
check the attachments...
refer
Google Issue 1438
also.
Regards,
Nil
posted 15 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
Yikes.. it's difficult to say what the exact source of your problem is without more information.
I would suggest a couple of places to look.
Are all your objects being returned by the RPC call serialized?
In my project we found the best type of objects to pass to the client are just plain old java objects (POJO's). If you can boil all your class fields down to primitives like String or int it works even better.
Remember the only thing you should be passing down to the client is the absolute minimum information needed for the Presenter (if you are using the MVP pattern) to render the display. Any business logic or complex calculations should be done on the server before generating your response.
I would suggest a couple of places to look.
Are all your objects being returned by the RPC call serialized?
In my project we found the best type of objects to pass to the client are just plain old java objects (POJO's). If you can boil all your class fields down to primitives like String or int it works even better.
Remember the only thing you should be passing down to the client is the absolute minimum information needed for the Presenter (if you are using the MVP pattern) to render the display. Any business logic or complex calculations should be done on the server before generating your response.
posted 15 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
Hi!
The idea about sending the minimum possible data is valid: check pages 32 through 34 in this presentation from the Google 2009 IO conference, and pages 14 through 18 in this other presentation from the 2010 conference. There were other conferences that pointed to this idea (sending id's instead of objects, for example) but I don't remember which -- sorry!
Hope this helps!
The idea about sending the minimum possible data is valid: check pages 32 through 34 in this presentation from the Google 2009 IO conference, and pages 14 through 18 in this other presentation from the 2010 conference. There were other conferences that pointed to this idea (sending id's instead of objects, for example) but I don't remember which -- sorry!
Hope this helps!
Great fan of Open Source, Linux, and web development with GWT; all of these come together for my ESSENTIAL GWT book!
| She's out of the country right now, toppling an unauthorized dictatorship. Please leave a message with this tiny ad: The new gardening playing cards kickstarter is now live! https://www.kickstarter.com/projects/paulwheaton/garden-cards |






