Differences - Search Results Caching and Drop Stacks
Posted: 07 Jan 2008 00:55
AFAICT, the fundamental difference is that caching is on a per-session basis and stacks is persistent through multiple sessions (until deleted).
Is it fair to say that caching is a necessary precursor to stacks?
I see drop stacks as being very similar in function to DOpus' "File Collections". Is this also a fair statement?
Can caching also be persistent? NB: I know you can add the contents of a search result tab to the Catalog, but I am concerned about seeing the cached results in the List.
Thanks,
-Jeff
Is it fair to say that caching is a necessary precursor to stacks?
I see drop stacks as being very similar in function to DOpus' "File Collections". Is this also a fair statement?
Can caching also be persistent? NB: I know you can add the contents of a search result tab to the Catalog, but I am concerned about seeing the cached results in the List.
Thanks,
-Jeff