I'm okay for blocking one part of the application or the whole for
global processing (login...). What I dislike is application blocking
me when I just ask for a little component to upgrade. Like if you have
a iGoogle page and click refresh on one widget block all widgets ;).
Olivier
On 10 juin,
+1.
When the user presses load / submit / ... on my app, I enable the
glass pane, and they have to wait until the submit has completed
successfully. I see nothing wrong with this approach:
PopupPanel loadingDialog = new PopupPanel();
loadingDialog.setWidget(loadingImageAnimation);
Carl,
Your proposal is interesting. But as a user, if I have to wait, I
leave... So many be an application needing some wait a minute popup
is not a good approach for the future. Imagine your browser putting a
popup each time a page is loading. Tabs will become useless, multi-
core computer too
I'm on the synchronous calls are the wrong approach side, but what
would really be useful would be some utility classes that allowed
synchronous like approaches.
Specifically :
- an async batcher that given a list of async services calls all at
once and then executes a specified action when all
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.
Ok, I see what you mean. I'm not sure about adding this feature but
maybe a better documentation about the bad idea of
On 17 mai, 08:37, 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
(Sorry, my message was incomplete)
Ok, I see what you mean. I'm not sure about adding this feature but
maybe a better documentation about the bad idea of using sync
request.
Olivier
On 17 mai, 08:37, mmoossen mmoos...@gmail.com wrote:
i completely agree with you Oliver!
i said already that i
I'm not sure about adding this feature but
maybe a better documentation about the bad idea of using sync
request.
http://code.google.com/webtoolkit/doc/latest/DevGuideServerCommunication.html#DevGuideGettingUsedToAsyncCalls
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
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
Hi,
Despite that i wrote the patch for sync-rpc, I completely agree with
kozura that in this case sync-rpc would be a bad idea.
BUT, who cares? if fomba wants to use it, it is up to him, if his
application is not responsive it is his problem not mine.
(this reminds me the apple-adobe conflict:
Michael,
I'm totally disagreed with you. When you choose to answer here, you
choose to give a good one. When you know someone is going the wrong
way, don't let him going to far. Fighting against problems is not a
good way to learn, you also need to have references.
Please, read again the
Hi,
when the RPC is complete you get an event
They are rare situations in which synchronous calls are appropriate.
One was discussed and contributed recently by mmoossen
http://code.google.com/p/google-web-toolkit/issues/detail?id=4898
Stefan Bachert
http://gwtworld.de
On 14 Mai, 17:05,
Hi, Is there a way of making synchronous calls in GWT using RPC. I actually
need something on the client side to ensure that the asynchronous processing in
rpc is complete. Can Anyone help?
--
You received this message because you are subscribed to the Google Groups
Google Web
Hi,
Doing synchronous call is globally a bad idea. What is your exact
need?
Olivier
On 14 mai, 17:05, fomba collins fomba_coll...@yahoo.com wrote:
Hi, Is there a way of making synchronous calls in GWT using RPC. I actually
need something on the client side to ensure that the asynchronous
We have implemented synchronous calls in our project, but we had to
make changes to the source code of GWT and create our own
distribution. It has been working well for us, but try and limit its
use to short calls to the server that run quickly since it will freeze
up all browsers completely
...@free.fr wrote:
From: Olivier Monaco olivier.mon...@free.fr
Subject: Re: Synchronous Calls with RPC??
To: Google Web Toolkit google-web-toolkit@googlegroups.com
Date: Friday, May 14, 2010, 8:41 AM
Hi,
Doing synchronous call is globally a bad idea. What is your exact
need?
Olivier
On 14 mai, 17:05
http://code.google.com/p/google-web-toolkit/issues/detail?id=4898
On 14 Mayıs, 18:05, fomba collins fomba_coll...@yahoo.com wrote:
Hi, Is there a way of making synchronous calls in GWT using RPC. I actually
need something on the client side to ensure that the asynchronous processing
in
For all those instinctively pushing for synchronous RPC whenever
somebody needs it, please! This is exactly a case where synchronous
network calls would be very bad, and just providing them because it's
easier to understand or whatever would mean people would design very
poor applications that
19 matches
Mail list logo
