Provided you don't include superfluous data in the JSON with the assumption that your web page will remove it, I don't see much harm in exposing the raw JSON.
Of course, you'll likely need dynamic data before long, in which case you'll want to pipe your JSON directly to the browser.
-----Original Message-----
From: Kevin Turner [mailto:kevin.turner@xxxxxxxxxxxxxxx]
Sent: Friday, November 11, 2016 12:16 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] JSON and the IFS
The point is that the JSON holds data and you are presumably downloading it to display it in something user friendly on the page - like a data grid or graph or something. However, if they user is savvy, they can just use the address bar to point at (and download) the raw JSON data as well, which might not be so good (depending on what is in it).
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
