I've started using timers combined with a state/transition matrix.
I've offered a simple example below. The basic idea is to keep a
'state' variable with the current state in the program logic. When
you initiate a asynchronous call, you move the state to LOADING.
When the call is complete, you
*Coding style*:
Several things. Why aren't your state variables part of an enum? Why
aren't you using a switch statement instead of 10 if/else ifs.
*Architecture*:
Why are you using a timer that will do nothing most of the time? You're
just putting load on the client unnecessarily. Why are
petrus schrieb:
Is there a possibility in GWT to communicate asynchronously from
server to client?
The term used in general for that is Server Push. A technique
for that is called Comet, so if you search Comet GWT with
the search engine of your choice, you should come up with a
couple of
Hello,
Is there a possibility in GWT to communicate asynchronously from
server to client?
The only solution which I've found is to use Timer as it's showed
there http://www.gwtapps.com/doc/html/com.google.gwt.user.client.Timer.html
, but then calls will be synchronous. What solution do you
On Wed, Apr 8, 2009 at 7:08 AM, Lothar Kimmeringer j...@kimmeringer.dewrote:
petrus schrieb:
Is there a possibility in GWT to communicate asynchronously from
server to client?
The term used in general for that is Server Push. A technique
for that is called Comet, so if you search Comet
Thanks for your advice! I'll try with comet.
On 8 Kwi, 13:08, Lothar Kimmeringer j...@kimmeringer.de wrote:
petrus schrieb:
Is there a possibility in GWT to communicate asynchronously from
server to client?
The term used in general for that is Server Push. A technique
for that is called
Vitali Lovich schrieb:
Calls in GWT are always synchronously, independent of the way
they are initiated.
Actually, they are always asynchronous.
I meant asynchronous, I don't know why I wrote synchronous.
They are single threaded though
if that's what you meant.
No, I simply
