Autocomplete enhancement: cached list for dropdown

[Oleg]

Hello Cagatay,

I have looked today dropdown feature in AutoComplete. Usable, but partually. Why do we ALWAYS need to send an ajax request (for completeMethod) to get all items from server? I would expect that list gets cached client-side without roundtrip to server when user clicks on "dropdown" icon next time. This is a similar concept what Tree or TabView have with "cache" attribute. Can you add this enhancement please?

Thanks for your effort.

[Oleg]

Hmm... I can't imagine that nobody is interested in cached list. Can I create a future request, Cagatay?

[shubforall]

@Oleg - it sounds very good...any update on this?

[Hamsterbau]

Sounds really nice, especially for small lists. But could blow up client side for large amount of data

[cagatay.civici]

It took 1 whole year to implement this complicated feature

http://blog.primefaces.org/?p=2577

[Oleg]

It took 1 whole year to implement this complicated feature

Better 1 year than never Good job, thanks. But after 1 year I don't need this features anymore . At least in current projects.

[cagatay.civici]

I'm pretty sure, someone else would need it

[Oleg]

Read the blog post... What I meant in the original post (1 year ago), was this feature:

User clicks on dropdown button in the Autocomplete --> list is fetched from the server --> subsequent clicks on the dropdown button should not fetch the list again if the caching is activated.

Does it work in this manner as well?

[cagatay.civici]

It should if search string is queried before regardless from input or dropdown.

[Oleg]

Well, assume the Autocomplete didn't contain search string before (was empty, no input was done). We click on the dropdown list --> list is fetched --> we click on this button again --> what will happen if the caching feature is active?