[Featureserver] Featureserver caching

david creane dc at openapp.ie
Fri Oct 5 13:46:56 EDT 2007


yes thanks Christopher that did work, just one question. 

Is there any way of caching the featureserver data that is sent to the 
browser, as in even the xml that is sent to the browser, could it be cached 
by squid, or some other from of caching. Or is that nonsense seeing as 
because someone can just keep panning to the left or right, that youd need an 
infinite number of cached files, unless you have a small number of panned 
step sizes if you know what i mean. Im just wondering if theres a way that i 
can be done, of is there even a point.

On a side note: This issue was annoying me for a bit and in case it comes up 
again. When the sql statement is generated from 
sql = "SELECT AsBinary(%s) as fs_binary_geom_col, * FROM \"%s\" WHERE %s = 
%%(%s)d" % (self.geom_col, self.table, self.fid_col, self.fid_col )
in PostGIS.py file, line 146. If i was to ask for a table called osi.roads  
the sql ends up as 

SELECT AsBinary(the_lines) as fs_binary_geom_col, * FROM "osi.roads" WHERE 
the_lines && SetSRID('BOX3D(2..........................00)) LIMIT 1000;

but this fails as it should be osi."roads" or osi.roads without parenthesis 
and not "osi.roads". Maybe instead of messing with code  just say in 
the /Docs/Datasource for people to be aware of it. Of course if i got this 
wrong ignore me :) .



More information about the Featureserver mailing list