Ryan Hoegg wrote: > Dave Kelly wrote: > >> Dave Kelly wrote: >> >>> cyrille wrote: >>> >>>> I don't know, >>>> but my idea is you do not get/set cookie via xmlrpcclient, >>>> but if the web server set a cookie on a xmlrpc response, >>>> xmlrpcclient will remember it, and send it back on next call.... >>>> >>>> isn't it ? >>>> >>>> cyrille >>>> >>> That's what I would have expected. >>> >>> However, the conversation I am seeing is that cookie is not being >>> retained. >>> >>> >>> >> I downloaded xmlrpc-1.1-src.tar.gz and looked through the >> XmlRpcClient code. There is nothing that is specifically related to >> retaining any header from the HTTP conversation. >> >> Have I missed something ? >> >> Dave. > > > No. The current version of XmlRpcClient does not support cookies. I > have an updated version on my system that supports cookies as well as > HTTP 1.1 but I am debugging interoperability problems with some PHP > XML-RPC servers. I foresee this being resolved soon. > > -- > Ryan Hoegg > ISIS Networks > > The API docs that exist on xmlrpc.helma.org and xml.apache.org both have the following for XmlRpcClient
A multithreaded, reusable XML-RPC client object. Use this if you need a full-grown HTTP client(e.g. for Proxy and Cookies support). If you don't need that, |XmlRpcClientLite| may work better for you. What is the Proxy and Cookies support that it refers to if the current version doesn't support cookies ?
