Opened 14 years ago

Closed 14 years ago

#3 closed task (wontfix)

serve MD-recod-detail from the cached recordset, by indexing the cached recordsets

Reported by: vronk Owned by: gaba
Priority: major Milestone:
Component: MDService Version:
Keywords: Cc:

Description

In the result of a query MDRepository sends back the whole MDRecords.
MDService translates the whole Resultset two some condensed view (tabular, list), linking two the detail-view for individual MDRecords. However currently actuating this link requires MDService to ask MDRepository for the individual MD-record by means of the MD record identifier: MDSelfLink, although it actually has the required data in it's own cache. It just isn't able to locate the right dataset and to pick the right record out of it..
The task is to implement an index of the cache, which assigns the resultsets with unique identifiers, that can be employed in the resultset view as back-reference to the cached data, which would be carried by the link to the MDRecord-detailview.

Change History (1)

comment:1 Changed 14 years ago by vronk

Resolution: wontfix
Status: newclosed

Meanwhile we totally rely on MdSelfLink? as Identifiers and the overhead of fetching the individual record from MDRepository seems acceptable.
Even if we would implement this for sake of efficiency, we can rely on the MdSelfLink?.

Note: See TracTickets for help on using tickets.