Repository save notification
3 answers
Thank you for the reply.
Is there any suggested work-around? The notification is only needed on the server side.
Here is the background information for this question:
Upon a client request, our REST service application fetches items from the repository, and does some processing based on the fetched data. The processed results are cached. For the same client request at a latter time, we would only want to fetch those items that have been modified in the repository, and do an incremental update on the processed results.
Is there any suggested work-around? The notification is only needed on the server side.
Here is the background information for this question:
Upon a client request, our REST service application fetches items from the repository, and does some processing based on the fetched data. The processed results are cached. For the same client request at a latter time, we would only want to fetch those items that have been modified in the repository, and do an incremental update on the processed results.
One option would be to build a query that represents "find items
modified after <date>". You could execute that query and fetch only
those results when needed. That should avoid the need for the save
notification.
-
Matt Lavin
Jazz Server Team
On Thu, 2009-02-12 at 06:47 +0000, wlu wrote:
modified after <date>". You could execute that query and fetch only
those results when needed. That should avoid the need for the save
notification.
-
Matt Lavin
Jazz Server Team
On Thu, 2009-02-12 at 06:47 +0000, wlu wrote:
Thank you for the reply.
Is there any suggested work-around? The notification is only needed on
the server side.
Here is the background information for this question:
Upon a client request, our REST service application fetches items from
the repository, and does some processing based on the fetched data.
The processed results are cached. For the same client request at a
latter time, we would only want to fetch those items that have been
modified in the repository, and do an incremental update on the
processed results.