× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Scott,

Yajl_getBuf() returns the pointer AND the length. I was just taking those same values and passing them to http_post. So I'm not sure why that would be a problem (provided it did this before yajl_genClose().

FWIW - I've switched to using the yajl_getBufStr() because it's easier (for me) to debug.

BTW: Thanks for both tools!

Greg

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, February 20, 2020 12:28 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: YAJL procedures

Hi,

Seems to me you should be using yajl_copyBufStr().  Definitely should
not be using yajl_getBuf() which simply returns a raw pointer to the
internal buffer... this seems like a disaster waiting to happen.  You
say you want to see the stuff in debug... I don't see how calling
yajl_getBuf() is going to achieve that?

-SK

On 2/20/2020 8:09 AM, Greg Wilburn wrote:
Thanks for the suggestions. I should have indicated that I'm working with a JSON web service.

Since I'm going to use this with http_post() (which uses a pointer). So I might as well do this and forgo the string? I just like to "see" stuff in debug.

yajl_endObj();
rc = yajl_getBuf(jsonPtr:jsonLen);
rc = http_post( URL
: jsonPtr
: jsonLen
: response
: HTTP_TIMEOUT
: HTTP_USERAGENT
: 'application/json');
yajl_genClose();




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.