I understand now & sorry for the confusion. It might actually be faster to do an ajax call to do the look-up because it will be asynchronous and have little impact on your ui. If for some reason you can't do that then use SpeedTracer to analyze where you client side code is getting bogged down. It is a great tool and can provide numerous insights as to where you need to focus your attention.
Jeff On Thu, Nov 18, 2010 at 9:41 AM, MickeyR <mnroo...@gmail.com> wrote: > Sorry, I probably was not clear. My entire story above is all > happening on the client-side. > So the search + display of results happens on the client, I'm not > making a RPC > to perform this. > > Currently I don't want to make any part of this server-side, so any > idea on how to > achieve this ? > > M. > > -- > 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-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- *Jeff Schwartz* -- 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-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
