Hi - > Ah, I had forgotten completely that file URLs worked out of the box > (libcurl, duh).
Yeah. > When we tried that way back when, the issue was just that it > actually does a libcurl fetch out of that path and saves another > copy of the file into the cache. Yes, a copy is made. This is "traditional" in the sense that the client code ensures that even if an original upstream server goes away, cached files stay accessible for a while. I can also see how this might be less valuable than just getting at the files with minimum overhead. Does anyone think we need to have both as options? - FChE
