scottklement.com

Please use [code] and [/code] around your code. You have been providing {code} and {/code} instead, and as you can see if you read your messages after you post them, this doesn't work. The path= option in the 2nd parameter to %XML is not for the file path. It is just the path of elements to extract ...

but... XML-INTO can read the file from the IFS for you, you dont' need to read it manually.

Go back to the example I posted earlier and see how it works. viewtopic.php?p=994#p994

open(), read(), write(), close() are UNIX APIs.
fopen(), fgets(), fputs(), fread(), fwrite(), fclose(), etc are ANSI C APIs.

Not sure which one is newer -- both date back to at least the 1970's.

I don't understand why you need to use any of these.... just let XML-INTO read the file.

Well, he's probably calling open(), but just to confuse us, has renamed it to fopen().... so the O_TRUNC is the likely culprit.

It'd be nice if he'd come on here and tell us that so we don't have to guess.

Sorry, I don't understand why you are searching for <Result> and substringing off all of the XML before it. Use the "path" option on xml-into so that this isn't necessary -- see the example I posted earlier. I already showed you how to make the whole thing work. I don't understand what you...

Well, if he were calling the open() API, yes. O_TRUNC makes no sense in the context of fopen()

This code makes no sense. You are writing the code as if you are calling the open() and read() APIs -- but your code says fopen and fread which are different APIs with different parameters.

Also, you posted this in the HTTPAPI forum, and it doesn't appear to be related at all to HTTPAPI.

When you post code, please put [code] before the first line of the snippet, and [/code] after it. This time around you posted a lot of code with very few explanations, and it is very hard to read. Sorry, I don't have time right now to go through and reformat the messages for you, like I did earlier....

I added the code tags because it was hard to read... Maybe that fixed the XML formatting problem, too.

yajl_writeStdout is pretty simplistic -- and doesn't have code to allow you to customize the headers. I could consider adding that if enough people are interested -- but you are the first one that's ever asked for it. You could, of course, use yajl_copyBufStr() or similar to get the JSON data into y...