It's hard to populate that grid of yours completely in the background since we have a singlethreaded environment. I'd probably even say it's not possible. So try to change your paradigm instead: if smth. happens (update) - users should know about it: - show a timer: time till next update - disable your grid while updating (glasspanel or smth.) - show update status You'll see - as long as users know what's happening and when it's happening they are all happy. And when they are happy - your are too ;-)
hth On 19 Mai, 08:25, Suren <[email protected]> wrote: > Hi All, > > Now as Carl mentioned, > > I tried using two different services with the same code, and in my > client, for initial Grid population I used the first service and for > the refresh, I used different service, which doesnt share any common > data or widget. > > But still I am having that problem.. > > I got the answer for the question I asked. But that ultimately ended > in not giving the result as I expect. > > Also I heard that no Javascript engine is capable for > multithreading..so obviously any javascript compilation will affect > the display of the browser..or gives a display hang kind of > impression.. > > Any thoughts are advise are welcome > > Thanks again > > On May 19, 10:19 am, Suren <[email protected]> wrote: > > > <module> > > .. > > .. > > <servlet path="/DBFetch" > > class="com.ibsplc.idaho.thinclient.server.DBFetchImpl"/> > > </module> > > > This is what I have now.. > > > Say if I am introducing new RPC named DBRefresh.. > > > What would be form of declaring it? > > > Also in my <client.appname>.java file, I have the following code > > > final DBFetchAsync dbFetch = (DBFetchAsync) GWT.create(DBFetch.class); > > ServiceDefTarget endpoint = (ServiceDefTarget) dbFetch; > > endpoint.setServiceEntryPoint(GWT.getModuleBaseURL() + "DBFetch"); > > > can I create a similar entry for DBRefreshAsync after the change in > > the xml file?? > > > Thanks > > Suren > > > On May 19, 10:16 am, Suren <[email protected]> wrote: > > > > Hi Carl, > > > > Thanks for the reply. > > > > >you could make a copy of the data to ensure the two grids are > > > >independent? > > > > I've tried this with the existing code..still I have the same issue.. > > > > >you could have one RPC servlet mapped to two different servlet > > > >paths - or even two serperate RPC servlets that both call common code. > > > > sorry for my ignorance..Did you mean the change to be made in > > > <app>.gwt.xml file ? > > > > Thanks > > > Suren > > > > On May 19, 8:14 am, Carl Pritchett <[email protected]> wrote: > > > > > > This is what happend : > > > > > Eventhough I am trying to populate into a new Grid, my previously > > > > > populated Grid is also affected..My Grid Display is lost..Only after > > > > > that population is done,..the grid is visible to the user.. > > > > > It would seem to me that this is caused by sharing some common data - > > > > perhaps you could make a copy of the data to ensure the two grids are > > > > independent? > > > > > > But I couldnt have two RPCs in a single client...servlet path and > > > > > mapping issues.. > > > > > I think that the issue above is the real issue, but to address this > > > > point - you could have one RPC servlet mapped to two different servlet > > > > paths - or even two serperate RPC servlets that both call common > > > > code. > > > > > Regards, > > > > Carl- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text - > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
