Kbase P26994: Why do dynamic object require more reading in the repository
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/13/2003 |
|
Status: Unverified
GOAL:
Why do dynamic object require more reading in the repository than static objects?
FACT(s) (Environment):
Dynamics
FIX:
A dynamic object such as a Dyn SDV does require more reading in the repository than a static SDV because the object is fully described in the repository. Indeed, each property/attribute of the dyn viewer and its contained field/widgets require one or multiple records in the repository. Although it requires more reading in the repository, the main goals are to:
1) Make a dynamic object have a smaller footprint than a static object, especially by using only one .r for the generic dyn viewer instead a .r for each static viewer master
2) Only dynamic objects can be managed by the Dynamics Web User Interface (developed in java, but using the same data in repository)
3) Keep the description of these objects in one central place (only described in repository), rather than deploying big .r master files on the client side.
There has been many achievements to improve the performance of dynamic objects since the early days of Dynamics, especially in 2.0A02 (SP2) by implementing the caching of objects on the client side. => once a viewer has been built, it is kept in memory for future use, so no need to read these records again to achieve it.