xerces-c-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alberto Massari <amass...@datadirect.com>
Subject Re: Several questions about Xerces-3.0
Date Mon, 27 Jul 2009 09:21:42 GMT
Same as for ICU: plain socket requires no external libraries, but it 
supports a very limited set of HTTP (no proxy resolving, no 
authentication, no compression, etc... it barely supports redirection); 
libcurl requires cUrl to be availbale, but it handles the full HTTP specs.

Alberto

Vyacheslav V. Yurkov wrote:
> 2009/7/27 Alberto Massari <amassari@datadirect.com>
>
>   
>> ICU gives you the capability of processing a lot more encodings than the
>> plain Xerces, but it requires you to bundle an external library that is
>> pretty big.
>> Did you add the -L<xerces path> -lxerces-c options to the link command line
>> ?
>>
>> Alberto
>>
>> Hi Alberto,
>>     
> thank you for your answer.
>
> I figured out what the problem was. Yes, I added -lxerces-c option but it
> was added at the beginning of the libraries list. I add it to the end of the
> list and application links with no errors.
> Can you also clarify the difference between plain sockets and libcurl?
>   


Mime
View raw message