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
