LCDS Caching and Paging

Question

How do we keep items in the LCDS data services cache independent between user sessions?  If I use session in the destination, I can still update an item in one users cache and have it change another users item (if the identity attribute is the same).
Another way to look at this question is that we want to use the data management services to enable dynamic loading and paging of large sets of data.  We don't want to utilize it for data management between sessions.
Thanks.
tj

Answer 1

Have you seen the part of the example configs where it talks
about what is required for data paging to work?
<!--
Indicates whether data paging is enabled for the destination
and if you wish to override the
pageSize set for the channel.
Setting the custom flag to true indicates that the
associated assembler has a paged-fill method
corresponding to each method specified via the
<fill-mathod> tag. The paged-fill method
should have two additional java.lang.Integer params at the
end of the parameters specified
via the <params> tag. The first param specifes the
index in the fill collection from which this
method will start retrieving records. And the second param
specifies the number of records to be
retrieved by each paged-fill call.
Default enabled value is false. Default pageSize value is
10. Default custom value is false.
<paging enabled="true" pageSize="5" custom="true"/>
-->
It seems to imply to me that you need the paged fill methods
in your config in addition to the regular ones.
I admit I have not got as far as getting a working paging
setup yet, although this is something I will need to get working in
the near future.