The number of projects there are is just amazing, but nothing seems to stand out.
- I don't like the idea of using Overlay Types since it's too much coding and the objects coded this way can be used only on browser-side
- I'm not sure what's the status of AutoBean (http://code.google.com/p/google-web-toolkit/wiki/AutoBean) since clicking on 'Project Home' here takes me to some I think very old start page for GWT. No official references from main GWT site https://developers.google.com/web-toolkit/
So given that piriti's code looks really nice and it's easy to switch between JSON and XML (if we ever needed),we'll try to go with that.
One issue we still have not resolved is the performance. We started with XML in the payload, since our apps work on SAP (ABAP is the language there) and it's easy to do XML on the backend rather than JSON. However, parsing of XML in the browser was not possible with piriti on some mobile platforms (Android) and using DOM library was both time consuming to code and really slow. Parsing of our payload took 5-7 secs on Android. This was unacceptable. That's why the switch to JSON.
The thing we'll test right now is piriti+JSON performance. I'm not sure how piriti does the parsing, but it might be that other frameworks do it faster/slower.
If anyone has an answer to the PERFORMANCE question of piriti+JSON, I'd be glad to hear.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/C0GWkTej1xIJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment