GWT Communication strategies -
i newbie gwt. doing feasibility study on gwt decide whether include in our product or not. went through various docs , have open questions. whether can use rpc( java-servlets) data other server well- means cross site access. see can via json or jsonp, wanted confirm on that.
may question sounds bad . not well-versed in web technologies well. web engines load balancing, case means browser gets reply , need not worry server gets result. how different cross-site access? why java-script not stopping accessing different servers in this?
then communication strategy better implement? know tricky question , requirement specific. in general 1 can proceed with.
i see many docs saying fine go gwt , no need have gxt in place. benefit when use gxt? have not worked on any. have worked on examples provided in gwt tutorial. needed know border-line between gxt , gwt ...
it great if 1 can clarify above doubts.
--priya.
gwt primariy client-side technology. have server-side related stuff related rpc mechanism (there may more server-side tech in 2.x versions, 1.7 user).
gwt's rpc allows write server-side logic in java , call services directly via java code (rather making request page returns json or other data , parsing data), , 1 of big plusses gwt. of course, on server side of things, can whatever want (including making connections servers on other domains). gwt manages rpc internally using proprietary binary format, in end it's fancy ajax. :)
gxt ui library gwt, giving fancy widgets , layouts, etc. demos give better idea of can do.
Comments
Post a Comment