Ticket #5 (closed defect: fixed)
Make URI-ref'd remote OMDoc elements accessible transparently
| Reported by: | clange | Owned by: | kristina |
|---|---|---|---|
| Priority: | major | Milestone: | zzz Future zzz |
| Component: | unknown | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Due to close: | YYYY/MM/DD | Include in GanttChart: | no |
| Dependencies: | Due to assign: | YYYY/MM/DD |
Description (last modified by kristina) (diff)
Dear Kristina, don't panic. I continued the discussion about loading referenced objects on demand a bit and create this ticket just as a placeholder that we don't forget it.
Ideas:
- have two constructors on every object: one for creating the object with the real data, the other one that takes an URI reference.
- Idea from Normen: JDOM maybe does something like this ("lazy loading", "loading on demand"), try to find an implementation by some guys who already did it.
- The real object should be loaded on demand, as soon as a method is called. This loading on demand should be implemented in a base class, maybe OMDocElement.
Update:
- Every method checks whether the object is already in the memory; if not, calls the download method to populate the fields in the object.
- Later, a method such as update() may be implemented, which writes the modified object back into the database.
Change History
Note: See
TracTickets for help on using
tickets.
