Re: HTTPAPI URL Post API Response Handling Options

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hi Ron,

You can use http_url_post_raw() to write your own handler that receives 
the data as it comes off the "wire" (the network).  Your handler can 
then store the data in memory, or wherever it likes.

For the Get operation, there's a similar http_url_get_raw() routine.

These have existed since the first release of HTTPAPI, they were some of 
the first routines written for HTTPAPI.


On 9/27/2010 8:55 AM, Ron wrote:
> Is there an Http_Url_Post* related API that allows me to designate
> that the response simply be put in a memory location (ie: variable
> address) as opposed to using the options that I'm aware of, which are
> either place the response in IFS file (and parse it myself) or setup
> callback procedure references and react to EXPAT parsing events. I
> have an interface to a web service that returns very small amounts of
> data and it would be nice to be able to take the returned string and
> parse it through use of built-in XML-SAX functionality. I can do that
> using the IFS file approach but I'm looking for every ounce of
> performance I can get.
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------