Of course,
but the result of the parsing of the getcapabilities response is an
umpredictable set of results.
So it is very hard to store in a structured cache (aka a db).
In a response capabilities of a wms 3.0 thereis many information , all
in multeplicitly N. And often optionally.
Also there the more complex of could be have a response "version=1.0",
"or "version=1.1" or "version=1.1.1" or "version=1.3.0" changing the
version mean changind the structure of the information and their structure.
So project a cache capacle to host in a structured structure the
information extracted from a parsing for all four kind of version is
really an huge work.
And all of this for a getcapabilites that more probably is absolutelly
unuseful when start a project.
:)
A.
Il 06/12/2015 14:52, Sandro Santilli ha scritto:
On Sun, Dec 06, 2015 at 02:31:52PM +0100, aperi2007 wrote:
Also I guess a the time lost is not only the request/response time, but also
the parsing time of the response.
A cache do not help on this.
It can ! Depending on what you cache, you may save
either (or both) download and parse time.
An URL could be mapped to a parsed content.
Or a content hash could be mapped to a parsed content.
Or both, to allow for caches of different lifetime.
--strk;
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
