On 12/11/2010 3:47 PM, Hraban Luyat wrote:
Maybe your website isn't all that serious, of course. In which case
you do not need caching in the first place, not in your either. I have
yet to come across a situation where actually doing /any/ caching
inside an app instead of with a caching proxy was anything else than a
bad idea. If somebody can enlighten me, please.
If there is a better way than doing my own caching, but here's my
problem. I have implemented OGC WCS, which is a web service for
publishing scientific data. Here's a typical data query:
http://128.252.202.19:8080/CIRA?service=WCS&request=getCoverage&version=1.1.2&identifier=VIEWS&BoundingBox=-130,24,-50,40,urn:ogc:def:crs:OGC:2:84&TimeSequence=2006-08-18&RangeSubset=SO4f&format=text/csv&store=true
There are three problems with proxies for this case:
- the response is two-step: service returns an envelope with a url to
the temporary file. The combination makes cache expiration a little
tricky, probably possible though, since the temp files are large and
they need to be cleared frequently.
- Some of these queries take a long time. It is quite common, that
second identical query comes in. In that case the second needs to wait
that the first finishes, and then return an envelope pointing to the
same temporary file.
- The data is in NetCDF files, which are very slow to open, a solution
is the same as a DB connection pool.
I put together a few lines of code to implement these all. If you know a
way to configure a standard proxy for this setup, I'd like to know it.
Kari
--
You received this message because you are subscribed to the Google Groups
"web.py" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/webpy?hl=en.
