uDIG

Cache georesource info and lazy load correct

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: UDIG 1.1.RC1
  • Fix Version/s: UDIG 1.2.0
  • Component/s: framework
  • Labels:
    None

Description

Implement the IGeoResouces so that they cache the information from the last loading locally and until resolve is called for a feature source or a datastore (or their "real" object) then use the cached information. When the "real" object is loaded then update the cached information with the real information. This should work the vast majority of the time since Services change fairly slowly. It will definately speed up browsing through the catalog and doing searches on the local catalog.

Issue Links

is duplicated by

Test - A new unit, integration or system test UDIG-1033 Test that catalog is lazy loading wrt titles at least.

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jody Garnett added a comment -
This is done by the two remote catalog implementations. The local catalog is not preserving a catalog info - we could consider holding the information we care about:
- ServiceInfo
- members
- member GeoResourceInfo title / icon / description / bounds?

And then issuing a REPLACE event when the real information is available.... ie when we are CONNECTED.

Proposal: Wraper Placeholder for NOTCONNECTED IService

This is the approach used by GeoTools and the existing external catalogs; the IService handle will return its own IServiceInfo, members including their own IGeoResourceInfo ... and when resolve is called for something other then this information they aquire the real resource and then delegate to it.

It is assumed a catalog REPLACE event goes out at this time causing layers etc to subst the fake wrapper for the real thing....
Show
Jody Garnett added a comment - This is done by the two remote catalog implementations. The local catalog is not preserving a catalog info - we could consider holding the information we care about: - ServiceInfo - members - member GeoResourceInfo title / icon / description / bounds? And then issuing a REPLACE event when the real information is available.... ie when we are CONNECTED. Proposal: Wraper Placeholder for NOTCONNECTED IService This is the approach used by GeoTools and the existing external catalogs; the IService handle will return its own IServiceInfo, members including their own IGeoResourceInfo ... and when resolve is called for something other then this information they aquire the real resource and then delegate to it. It is assumed a catalog REPLACE event goes out at this time causing layers etc to subst the fake wrapper for the real thing....
Hide
Permalink
Jody Garnett added a comment -
bug brought forward to UDIG1.2.M4 visibility
Show
Jody Garnett added a comment - bug brought forward to UDIG1.2.M4 visibility
Hide
Permalink
Jody Garnett added a comment -
This issue has been addressed by storing some information (such as title) out with the catalog state (as a big xml file). In terms of API this is shown as an IService persisted property.
Show
Jody Garnett added a comment - This issue has been addressed by storing some information (such as title) out with the catalog state (as a big xml file). In terms of API this is shown as an IService persisted property.

People

  • Assignee:
    Unassigned
    Reporter:
    Jesse Eichar
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: