GWT on client side is single thread, right? There is no any concurrent problem at all!
2010/1/21 JayFo <[email protected]> > Yes. Consider: > - GWT component 1 calls GWT async service A. Processing starts on > server-side. > - GWT component 2 calls GWT async service A. Processing starts on > server-side. > - Async responses from both calls to service A arrive more or less > simultaneously on the server-side. > > Any caching logic implemented on the client side would presumably want > to keep a cached copy of the results, but would also have to be > careful to be thread-safe so as to accurately store the data returned > by both calls to service A. > > On Jan 20, 10:34 am, Alexander <[email protected]> wrote: > > Concurrent async results? > > > > BTW Im interested too in cache approach. > > > > 2010/1/19 JayFo <[email protected]> > > > > > > > > > The GWT application I'm developing (GWT / Spring / Hibernate) returns > > > some large resultsets for the async service requests that feed its > > > pages. Caching these results on the server-side saves me some > > > processing, but I can't avoid the serialization and deserialization > > > required to send it to the UI. From profiling my application, I know > > > that this is the main performance bottleneck right now. So, I'm > > > considering implementing a centralized client-side caching system. I > > > would rather not leave it up to each widget or page to figure out what > > > data to cache and how to cache it - something transparent would be > > > better. The issues I need to deal with are many: handling concurrent > > > async results, keeping the cache size to a maximum so as not to lag > > > the browser, write-through issues, cache invalidation... the list goes > > > on. > > > > > Has anybody tried this? How did you do it, and how well did it work? > > > Am I barking up the wrong tree? It sure would be nice if GWT had a > > > standard approach / framework for this. > > > > > Thanks in advance! > > > > > -- > > > 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]> > <google-web-toolkit%[email protected]<google-web-toolkit%[email protected]> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > > Regards, > > Alexander > > -- > 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. > > > > -- Regards, Alexander--
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.
