- From: Robert O. Morris <Robert.O.Morris@jpl.nasa.gov>
- Date: Tue, 25 Jul 2000 08:33:36 -0700
- To: <www-lib@w3.org>
- Cc: "Robert Morris" <Robert.O.Morris@jpl.nasa.gov>
When using the client-side caching code in the library, I see that it doesn't handle spaces in the pathnames to the cached data in the .index files. The .index file appears to be parsed using spaces to separate the fields. When the Path to the cached data in the .index file contains spaces, the .index file will be parsed incorrectly and caching won't work. This is particularly important under windows 2000 and I believe Windows NT also. Spaces in pathnames are allowed on those platforms - and for user-specific directories (where user's programs pretty much have to write in the absence of administrator priveledges) dictated. "Don't use spaces in pathnames" doesn't appears to be a viable solution in my case. My Linux box also allows spaces in pathnames, but while still relevant - that's much less important to me. Converting the path to the cache directory to windows "short names" doesn't appear to be a solution that holds up under close scrutiny (and would fail anyway on file systems that don't support short names). If it hasn't already been considered, I'd like to see a more robust set of delimiters in the .index files that allow spaces in pathnames - "" for instance. I tried to find a patch or past emails about this problem, but to no avail. If the problem is solved or is already under considerations - it would be really nice if someone would tip of off with a quick note. Thank You ! Rob Morris
Received on Tuesday, 25 July 2000 11:33:38 UTC