Member
2007-06-13, 12:29 PM
I'm no programmer, but I am a highly skilled professional thinker. :-)
My idea would be to have OF treat archived items differently. Not address them until *I* address them. That is, while I'm working in my day-to-day and not looking at past triumphs, to not have them addressed via the program or memory space. Some virtual sequestering, if you will.
When I invoke a view that has my archived items, or if I click the tick-box to include archived items in a search (like that little feature request just sliding in there??) then and only then are they referenced by the program and its memory space. Then and only then will they be addressed, and when I exit the view or the search, etc, ideally they would be pruned from the active heap and sequestered again.
Does that make sense?
Of course, this might be completely impossible from a programming standpoint. Perhaps tracking archived items in a separate but parallel db?
FWIW.
Last edited by dashard; 2007-06-13 at 12:31 PM..
Reason: edited for spelling