Re: receiving POST encoded in JSON

Henrick,

The post I made was not meant to be an all inclusive answer that one can
just implement.

It was showing the concepts required to solve the problem. I prefer to
take the "teach them to fish" route as learning is more valuable than just
pasting code. If someone wants a full application I'm happy to help and
bill for that. :)

As for the special characters (at least #), that's easily fixed. And,
actually they will work fine on CCSID 277 and 280. I hope they don't have
to twitter if that # is no good. :)

As for "answering back" I'm not sure what you mean by that.

And, the QtmhRdStin comment, yes... but I'm not going to guess on the setup
of the server for each case. YMMV.

It's great to hear you've worked with the OP to solve the issue. Why not
post your solution to the problem here (or somewhere else) for others to
see? That would be much more beneficial to everyone.

Brad
www.bvstools.com

On Mon, Aug 3, 2015 at 12:18 PM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

@Bradley


First of all, Pat runs on a machine with Italien EBCDIC CCSID so your
sub-procedures
will not work since # in US is x'7B' and in Italian is x'B1' where x'7B' is
£.

In general if you use $, # or @ and any of these characters are moved
elsewhere
in the CCSID you may be in trouble.

here you have an overview of EBCDIC code pages ...

http://www.easymarketplace.de/codepages.php


Secondly your example will probably hang up some clients or throw an HTTP
error back since you don't answer back.


Thirdly the example has another missing bit ...

When you receive data through QtmhRdStin the data you will receive will
either be in EBCDIC or in ASCII/UTF-8 depending on the MIME Content-type
the client choses to use:

If the content-type is text/... Apache automatically converts from
ASCII/UTF-8 to EBCDIC

if any other content-type is received the data passed by qtmhRdStin is in
the original
received CSSID typical either ASCII or UTF-8.

The QtmhWrStout functions the same way with a twist ...

if you write out a content type: text/...; charset=xxxxx no conversion is
done of data by
Apache.


PS.

I have worked with Pat during the weekend to establish a HTTPAPI client and
a
receiving powerEXT program using a combination of both and YAJL.