which is better gwt-rpc or json when considering several factors listed below -
queries on gwt rpc , json
- first of all,is correct compare both?
- which 1 best technology server communication?
- which kind of applications better go gwt rpc , go json?
- which 1 efficient in performance?
- if app brings huge data server client every request good,rpc / json?
- i'm developing 2 apps, 1 gxt(a web app) , other 1 mgwt, technology web app , mobile app. i'm beginner,pls clarify queries. in advance
1) can compare them. have use cases both gwt-rpc , json in our 200+ screen enterprise product ( in gwt ) 2) there no single choice answer query. each flavour of gwt server communication has pros-cons.
3a) gwt-rpc best suited crud-application when client server side data provider/consumers coded in java. gwt-rpc lends easy optimisations , code-refactorings.
3b) in our use case found json best suited data consumption when api's output need consumed other clients can coded in php/javascript/android/ios. generate json data on server side , serve them via rest services. have gwt client consumes json data render charts.
4) gwt-rpc more efficient use case i.e client in gwt code.
5) should never design huge data. @ given point of time user can see "one screen" of data. why fetch lots of data? 6. gxt sencha , have mobile focused library apart that. mgwt might choice open source , developer got hired part of gwt team !!!
Comments
Post a Comment