Thank you .... - Sunit Katkar http://sunitkatkar.blogspot.com/
On Sat, Nov 20, 2010 at 3:10 PM, Thomas Broyer <[email protected]> wrote: > > > On 20 nov, 23:23, Sunit Katkar <[email protected]> wrote: > > But if I return a Request as the return, then what about the data that is > > supposed to come from server? > > It's Request instead of void, in your *Async interface, where the > result comes back into an AsyncCallback. > > """The nature of asynchronous method calls requires the caller to pass > in a callback object that can be notified when an asynchronous call > completes, since by definition the caller cannot be blocked until the > call completes. For the same reason, asynchronous methods do not have > return types; they generally return void. Should you wish to have more > control over the state of a pending request, return Request instead. > After an asynchronous call is made, all communication back to the > caller is via the passed-in callback object.""" > — > http://code.google.com/webtoolkit/doc/latest/DevGuideServerCommunication.html#DevGuideRemoteProcedureCalls > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
