Re: [soaplite] Re: forcing base64 in XMLRPC::Lite
> So at least it's in the ball park as a custom solution, which is aTrue, it could make a difference sometimes, esp. for CGI apps,
> lot better.
because it doesn't need to initiate XML::Parser. yet keep in mind
that XML::Parser::Lite doesn't do entity decoding, so you have to do
it on application level if you need to. Future versions may support
entity decoding. If you do base64 you shouldn't have any problem
Best wishes, Paul.
--- mrdamnfrenchy@... wrote:
> Hi Paul,__________________________________________________
> I did force to use XML::Parser::Lite, and that made a huge
> difference. Encoded as a string, it now takes 5.3 seconds instead
> of 18 seconds. Encoding it as a base64 is a bit slower (6.5
> So at least it's in the ball park as a custom solution, which is a
> lot better.
> > > Is there a way to force SOAP::Lite to use XML::Parser::Lite?
> > > that be faster?
> > Yes, you can do it with $SOAP::Constants::DO_NOT_USE_XML_PARSER =
> > somewhere after 'use SOAP::Lite', but before actual calls.
> > I don't think it'll make a difference for you and here is why:
> > > The same data set (4.2Mb) takes >60 seconds in XMLRPC embedded
> as a
> > > string, 18 seconds as a base64, and 4 seconds with some simple
> > > interface instead of XML-RPC. Clearly, expat is the bottle
> ------------------------ Yahoo! Groups Sponsor
> To unsubscribe from this group, send an email to:
> Your use of Yahoo! Groups is subject to
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger