Re: JSON and the IFS

[Henrik Rützou <hr@xxxxxxxxxxxx>]

The problem is on the IFS that you may write a UTF-8 file on your PC that
has no CCSid
and then dump it in the IFS.

The CCSid then becomes CCSid 1252 even though it actually is CCSid 1208
this may cause
AJAX and DOM to go down.

On Tue, Nov 15, 2016 at 7:04 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

> If the data changes seldom, I don't see any reason not to make it static.
> As for security, that question has to be addressed whether the data is
> static or dynamic.
>
>
>
> -----Original Message-----
> From: Booth Martin [mailto:booth@xxxxxxxxxxxx]
> Sent: Monday, November 14, 2016 1:10 PM
> To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
> Subject: Re: [WEB400] JSON and the IFS
>
> Would this be an "it depends" situation?  Take this particular example,
> for instance.  The data changes once every 4 years or thereabouts why
> format the result every time its accessed?
>
> The second part of this would be a response dealing with management's
> comfort level of letting just anyone into production data, even if it is
> read-only.
>
> Still, the point is well made; for the iSeries to cast off the pallor of
> old age we do need to be able to access real & original data on the fly.
>
>
>
>
> --
> This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
> list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.