problem in libURL...

Jan Schenkel janschenkel at
Mon Feb 7 14:42:01 EST 2005

--- Trevor DeVore <lists at> wrote:
> On Jan 29, 2005, at 12:14 PM, Andre Garzia wrote:
> > I am at 2.5 release... after rebooting the machine
> libURL started to 
> > behave better.... guess what there's a strange
> thing with XML-RPC lib, 
> > the one that taps into revXML that taps into
> libURL anyway. For 
> > example revXMLRPC_CreateRequest is a handler, but
> if you call it as if 
> > it is a function by using parenthesis, it will not
> return an error, it 
> > will return fine, but it will never work and the
> errors will be 
> > related to libURL... heck.... no xmlrpcerr:
> something, but things like 
> > "socket timeout" and stuff. I always thought that
> if you call a 
> > handler using a function call it would never reach
> it's destination. 
> > strange.... very strange...
> Andre,
> I've been on vacation so I am answering this a
> little late but if you 
> are using the XML-RPC library you need to reset the
> httpHeaders after 
> any call to revXMLRPC_Execute since it sets the
> headers but never 
> empties them.  I have filed a bug report on it which
> you can see here:
> Getting the timeout error is consistent with the
> behavior I saw when 
> working with XML-RPC.
> -- 
> Trevor DeVore

Hi Trevor and Andre,

You'll be glad to hear tht I've fixed that oversight
for the next version. However, I was not aware of a
timeout error.
And revXMLRPC_CreateRequest is a _function_ not a
command, and it returns an internal ID, which just
happens to be the XML tree that is used for storing
the request, and points to oher data in the XML-RPC
library internal data structures.
I think I've covered most of the reported bugs in the
XML-RPC library, but if you encounter something that
isn't in bugzilla, please do so asap, so I can get on
top of it.

Best regards,

Jan Schenkel.

Quartam - Tools for Revolution

"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)

Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less.

More information about the use-livecode mailing list