This question is related to the Tracked Resource Set 2.0 specification: http://open-services.net/wiki/core/TrackedResourceSet-2.0/
Since the base set can be paged, and for very large collections, the paging can be unstable, it would be useful to include the cutoffEvent property in every page with a possibly changing value. The specification indicates that the first page MUST include a cutoffEvent property, but doesn't seem to prohibit also including the cutoffEvent property also in subsequent pages. This is particularly useful if pages in base are shown in order of increasing modification time, which is the case in our implementation. Of course in that case, a resource can appear more than once in the base set if it is modified while someone is paging. Are there any issues with this implementation from a spec perspective? ================================================ Joe Ross/Austin/IBM, [email protected] Tivoli Autonomic Computing & Component Technologies 512-286-8311, T/L 363-8311
