Hi -
I was having some problems with WSDL caching in windows. Ticket #360
addressed/fixed my immediate concerns, but in the process of understanding
that, I came up with a questions:
It looks like options.cachingpolicy may have originally been intended to
specify whether WSDL's are cached as XML or as pickled objects.
But as implemented (in 0.4.1,) it looks like
- options.cachingpolicy effectively turns caching on or off, and
- WSDL's are always cached as pickled objects (never as xml)
Is this true?
Here's some analysis on the topic:
- The default options.cachingpolicy is 0
- The default cache for a Client is ObjectCache
- ObjectCache only saves pickles
- The Client uses DefinitionsReader to read (and cache) the WSDL
- DefinitionsReader does not cache anything unless options.cachingpolicy==1
- DocumentReader and DocumentCache would be used to cache WSDL's as XML -
but it doesn't look like anything is using them.
I'm thinking that DocumentReader/DocumentCache should be marked as
deprecated if they are not actually used. But I'd rather see cachingpolicy
used to swap between XML and pickle caching. I'd be glad to write a patch
for this if I'm on the right track.
Any clarification would be appreciated. Thanks.
-- Jeff
Show replies by date