Project PSIworld - Tasks: task #6529, Client prototype caching
You are not allowed to post comments on this tracker with your current authentication level.
task #6529: Client prototype caching
Submitter: | Tolga Dalman <tolgadalman> | ||
Submitted: | Thu 15 Feb 2007 09:36:23 PM UTC | ||
Should Start On: | Thu 15 Feb 2007 12:00:00 AM UTC | Should be Finished on: | Thu 15 Feb 2007 12:00:00 AM UTC |
Category: | PSIobjapi | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-f8d8.
Corresponding source code
Unlike object instances (graph leaf), prototypes are assumed to be changed rather seldom.
Thus, a client reading an object property may cache locally an set of cache objects. When a request for a prototype is sent to the server, a version number is supplied along with the prototype id. The server responds with the full prototype object, or OBJ-UP-TO-DATE.
Thresholds will help tweaking performance:
- size of total client cache
- minimum size of a prototype object