Opened 16 years ago
Closed 16 years ago
#681 closed enhancement (fixed)
Implement caching for DESCRIBEFEATURESCHEMA
| Reported by: | ksgeograf | Owned by: | ksgeograf |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Maestro | Version: | |
| Severity: | trivial | Keywords: | |
| Cc: | External ID: |
Description
As reported by Maskim, RuntimeMap generation can benefit greatly from caching the results of the DESCRIBEFEATURESCHEMA call. This is in addition to the caching proposed in the Rfc's. This enhancement will prevent large xml documents from being transmitted back and forth.
Change History (4)
comment:1 by , 16 years ago
| Status: | new → assigned |
|---|
comment:2 by , 16 years ago
comment:3 by , 16 years ago
Yes. Initially, I will provide a local cache for the runtime map generation. I will then make a flag that keeps this cache on the connection. And finally a method to explicitly clear the cache.
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I have now added three methods (r3305): GetFeatureSourceSchema GetFeatureSourceDescription ResetFeatureSourceSchemaCache
The two first methods try to cache as much information as possible. The runtime map generation has been updated to call these methods.
By keeping the other methods as direct connections, it is possible to choose between cached and non-cached calls.
Can you include a method to flush this cache?