Re: is calling RequestFactory a blocking call ? when to update the View upon return of RequestFactory?

You REALLY need to read up on GWT RPC. > requestFactory > .employeeRequest() > .findAllEmployees() > .fire(new Receiver>() { > @Override > public void onSuccess(List response) { > > ##

Re: is calling RequestFactory a blocking call ? when to update the View upon return of RequestFactory?

*within Receiver#onSuccess anonymous inner class*, it's where you actually receive the data. *After that code* the data is not yet available. -- 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-w

Re: is calling RequestFactory a blocking call ? when to update the View upon return of RequestFactory?

calling setWidget, should be done within Receiver#onSuccess anonymous inner class, or after that code ? On Jan 17, 7:17 pm, Y2i wrote: > The call is non-blocking. > > When response arrives, you can populate the widget and call setWidget() on > the display.  Start() > javadoc

Re: is calling RequestFactory a blocking call ? when to update the View upon return of RequestFactory?

The call is non-blocking. When response arrives, you can populate the widget and call setWidget() on the display. Start() javadoc

is calling RequestFactory a blocking call ? when to update the View upon return of RequestFactory?

I am facing a dilemma. when an Activity starts, I use RequestFactory to retrieve some data. - I don't know however when should I update the view responsible for displaying the data. in the code below, I have identified two place holders ## A ## and ## B ### and another question: - is a call on R