I have just finished adding the first set of changes necessary to enable
Xerces-C to process HTTP system id's. It will now allow you to specify
a HTTP URL to the remote XML file, DTD, or external parsed entities.
The implementation is based on raw system 'socket's and needs no third
party libraries. At this point it has been minimally tested under Windows
NT (uses WinSock), and the listed Unix's (Linux, Solaris, AIX,
HPUX using aCC).
LIMITATIONS
-----------
The implemenation does no special processing for going through a firewall
or gateway. Further, it only connects to port 80 of the destination machine.
TODO's
------
What remains to be done:
- define new error handling messages and throw appropriate exceptions
- call the XMLURL method to get the port number in the URL and use that.
This method has to be added to the XMLURL class.
- Special characters (like spaces etc.) in URL's are not escaped.
FOR NOW YOU WILL HAVE TO BUILD BINARIES YOURSELF
------------------------------------------------
To get this functionality, you will have to get the latest set of
sources from the repository and generate the binaries yourself. Any
tarballs later than 6pm PST, Mar 20, 2000 should have the new files
in them.
Under Windows, just click on the 'xerces-all.dsw' file and 'rebuild all'.
The XercesLib.dsp project file has been modified to use the
WinSockNetAccessor.
Under Unix, additionally specify '-n socket' as arguments to 'runConfigure'
in the src directory, to use this SocketNetAccessor implementation. By
default, it runConfigure script continues to use the fileOnly NetAccessor
implementation.
WISH LIST
---------
If anyone knows what additions are needed to enable this to work
through a firewall/gateway, that would be valueable contribution.
NEED FEEDBACK
-------------
I would be very interested in getting feedback on this implementation.
Please let me know what works and what does not.
Please send all feedback to [EMAIL PROTECTED]
rahul
