a) You could cache the results in your page or component class, but
b) Caching the results is probably a bad idea since the results are
going to change depending on what the user types, and whether they
continue typing once the first results come up.
It sounds like you really need to spend some time optimizing your
query to execute faster. Other thoughts are to return the top n
results for any given query string.
Robert
On Feb 10, 2010, at 2/106:54 AM , Stephan Windmüller wrote:
Hello!
I just experimented with the autocomplete AJAX mixin. The values are
generated correctly, but the response is very slow. This is caused
by the database lookup which takes very long to retain all objects
and retrieving the label for them.
Is it possible to cache the list of Strings somehow for this mixin
to speed things up?
Regards
Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
