Hi - <br><br>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:<br><br>It looks like options.cachingpolicy may have originally been intended to specify whether WSDL&#39;s are cached as XML or as pickled objects.  <br>
<br>But as implemented (in 0.4.1,) it looks like <br>  - options.cachingpolicy effectively turns caching on or off, and <br>  - WSDL&#39;s are always cached as  pickled objects (never as xml)<br>Is this true?<br><br>Here&#39;s some analysis on the topic:<br>
 - The default options.cachingpolicy is 0  <br> - The default cache for a Client is ObjectCache <br> - ObjectCache only saves pickles<br> - The Client uses DefinitionsReader to read (and cache) the WSDL<br> - DefinitionsReader does not cache anything unless options.cachingpolicy==1<br>
 - DocumentReader and DocumentCache would be used to cache WSDL&#39;s as XML - but it doesn&#39;t look like anything is using them.<br><br>I&#39;m thinking that DocumentReader/DocumentCache should be marked as deprecated if they are not actually used.  But I&#39;d rather see cachingpolicy used to swap between XML and pickle caching.  I&#39;d be glad to write a patch for this if I&#39;m on the right track.<br>
<br>Any clarification would be appreciated. Thanks.<br><br>  -- Jeff<br><br>