Matt Sergeant writes: > First of all, do you know that both XSP and LibXSLT will read gzipped files > already? I haven't tried it, but libxml2 has built in support for gunzipping > on the fly.
No, I didn't know that. I will look into it. My approach was that AxKit was generating an "Internal Server Error" whenever I accessed "sample.xml" or "sample.xml.gz" because "sample.xml.gz" was the only file on the system. I saw in the error log that the parser was complaining: [AxKit] [Error] xmlParse returned error: 4, Start tag expected, '<' not found so, assuming the parser could not handle gzipped files, I patched Provider::File to decompress the file before the parser got to it. But I will try to find out how to get the parser to handle the compressed input directly. > Secondly, this is best implemented as an alternate provider. See the > AxContentProvider and AxStyleProvider options. Just subclass the File > provider and implement the get_fh and get_strref methods. That sounds ok except for one possible drawback (correct me if I'm wrong): multiple providers that provide "one extra feature" without the ability to use features from different providers at the same time (because only one provider is used to process a request). For example, I see that a new FileWrite.pm was submitted in CVS. How would a user be able to select FileWrite capability in conjunction with GzFile capability? (Maybe this isn't a good example.) Thanks for the quick response! Ken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
