Re: JSON

[Pete Helgren <pete@xxxxxxxxxx>]

I find that an interesting request because unlike XML, JSON was designed 
to be consumed by a browser or server with a JavaScript interpreter.  
JSON represents an object in text and when rendered produces an object 
for JavaScript to use.  Most JSON I have worked with or created has both 
data and JavaScript functions so using it to transport data between 
non-JavaScript capable servers is an interesting use case.

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java

On 9/20/2013 7:57 AM, RPGLIST wrote:
> Is there a native JSON parser for the i?  One of our c# guys uses it for
> EDI and suggested that it might be something we could use for sending data
> to and from the iSeries.
>
> As I've mentioned previously I can have up to 99 lines of around 12k per
> line and if I use XML that will probably double in size so abouty 240k per
> transaction.  Not huge but using a stored procedure has already given us
> headaches since he keeps getting an error that he's exceeding the 32767
> char limit, and yes I have the fields in the RPG defined as SQLTYPE CLOB.
>
> I know a web service would probably be the cleanest way to handle the
> transaction, but we've not done that and I've asked the systems guys to
> turn it on, but that has to go through channels and I haven't received an
> answer yet.  The owner however, is very much against opening the iSeries
> to the outside world.
>
> If someone has a better idea or suggestion I'm all ears.  socket
> programming is out for now, nobody here has the expertise and we don't
> have the time for OJT.
>
> Dutch