Ok, If Xerces will use the APIs provided by libcurl, then what Xerces's APIs must I use to get Xerces to recognize my proxy settings or how does Xerces determine the proxy settings? I've tried googling for the answer, but came up empty. I'm not sure of the right text combo to get a hit.
Thanks -----Original Message----- From: Alberto Massari [mailto:[email protected]] Sent: Tuesday, November 03, 2009 11:27 PM To: [email protected] Subject: Re: What is the difference between configuring Xerces 3.0.1 with--enable-netaccessor-curl vs --enable-netaccessor-socket? If you use --enable-netaccessor-socket you will not be able to specify a proxy, as the code that reads from the Internet is simply working with plain TCP sockets. If you use --enable-netaccessor-curl Xerces will use the APIs provided by libcurl, so if you use the same API to setup a global proxy, you will be able to use it. Alberto Dantzler, DeWayne C wrote: > > Hello > > Problem: there is a proxy between Xerces and the outside World and I need > Xerces to perform XML validation against a schema which includes online > references to an external scheme (e.g <xs:import > namespace="http://www.w3.org/myspace > schemaLocation="http://www.w3.org/schema.xsd"/>. > > What is the difference between configuring Xerces with > --enable-netaccessor-curl vs --enable-netaccessor-socket? Basically, how does > this effect the socket behavior of Xerces and why would I choose one over the > other? > > Thanks > >
