× 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.



Alvin,

200%20MAIN%20ST isn't JSON. There is no need to encode blanks in JSON, it'd simply be { "street": "200 MAIN ST" } but if you had to encode something, it'd look like this: { "street": "200\u0020MAIN\u0020ST" }

What you have is HTTP URL Encoded data. To decode it, you can call the SQL URLDECODE function https://tinyurl.com/47wexvzz


On 4/12/2022 8:12 AM, Alvin Strasburger wrote:
Jon,
How to receive the JSON is our exact problem. We can parse a JSON-like
string perfectly with DATA-INTO using a test string in our program. Our
issue is the front end of how to receive the 'decoded' JSON doc. Our past
experience is receiving comma delimited strings with no other punctuation or
blanks. Now with trying to receive names and addresses, we end up getting an
address element like 200%20MAIN%20ST instead of 200 MAIN ST. So in short, we
don't really understand how to get the decoded JSON doc to the RPG/YAJL
parser from the CGI interface.


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.