Reindeer - Tasks: task #10265, Immutable resources
You are not allowed to post comments on this tracker with your current authentication level.
task #10265: Immutable resources
Submitter: | Patrik Olsson <peo> | ||
Submitted: | Sat 13 Mar 2010 08:35:01 PM UTC | ||
Should Start On: | Fri 12 Mar 2010 11:00:00 PM UTC | Should be Finished on: | - |
Category: | libreindeer | Priority: | 3 - Low |
Status: | None | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Planned Release: | None |
Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one
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.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-03-13 | peo | Dependencies | - | task #10264 is dependent | |
2010-03-13 | peo | Should be Finished on | 2010-03-12 | - |
Powered by Savane 3.13-bb6a.
Corresponding source code
It should be possible to create some resources as "immutable". Backends can check if something is immutable and optimize the use of the resource if that is the case (for example, checking for updates is not necessary).
Immutable means the application promise to not change the resource and it is undefined behavior if they do anyway.
RenUsage could be used for at least all basic types (those that keep track of raw data), and a new value (e.g. REN_USAGE_IMMUTABLE) for this enum would mean immutable. Some types perhaps don't need the whole range of RenUsage values so a boolean is enough.
Note that backends could still use back data keys on immutable resources, it is just that the update callbacks will never be called for these resources (except for the first time).