i still see many people trying actually to use async calls only because they do not have any choice and without understanding the idea (and trying to fit async calls in sync design).. i think that if beginners could start with sync requests, and see the problems with them, they will better learn and appreciate async requests. for me the best would that GWT gives you the possibility to use sync calls but of course with big enough warnings. as javadocs like this: DO not use this unless you REALLY know what you are doing. the recommended way is to use async calls + a link to a good online explanation, etc...
and btw thanks to everyone for discussing, i think that discussing here this kind of issues is just the best for everyone ;) regards, Michael On May 17, 4:55 pm, kozura <koz...@gmail.com> wrote: > Many languages restrict what you can do when that thing is practically > never a good idea given their design model - Java doesn't let you > access pointers so developers can stick their scissors in the > proverbial pointer-arithmetic electrical outlet. Even your issue had > nothing to do with the async nature of RPC, but rather with an error > popping up, and your solution was to wait for the RPC call to return > before allowing the browser to continue - a hack to solve your issue. > I've yet to see an example where sync is a good choice, much less a > requirement. Just as the GUI interface reflects the asynchronous > nature of user interaction, so the GWT RPC interface reflects the > unreliable async nature of client-server communication; a synchronous > option simply does not match the model! > > Here's where I disagree with the "give them the choice" argument. If > GWT were to provide such a feature, new developers would use it (seems > much easier!), design large applications around it in their local dev > environment, and instead of learning from it when the deployed app > runs into problems, would demand new features to try to make that > programming model work. It's not a smooth slope of "ok now lets go > more advanced and switch from sync to async"...retrofitting is hard > and ugly! Instead GWT forces you to understand this issue up front, > when you can do a better clean design that fits the problem. > > On May 17, 12:37 am, mmoossen <mmoos...@gmail.com> wrote: > > > > > i completely agree with you Oliver! > > > i said already that i think that sync-rpc is a really bad idea in this > > case. which was already addressed in detail by you and others. > > > my point was against the spirit of the gwt team to do not give the > > developer the choice to use sync requests if he wants to. > > it is like never letting a child to cross the street alone instead of > > teaching him to watch out. > > > what we need is better developers and the way to achieve that is to do > > mistakes and be willing to learn, and not a tool that tells you "i do > > not allow you to do that because it *might* be a bad idea"... > > > regards, > > Michael > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
