|
> > I just don't know enough about SPA development patterns to know what > might, or might not, be good ways of dealing with these issues. It appears to me that you have settled on an architecture where the SPA consists of STATIC HTML, CSS, JavaScript; a yet-to-be-defined PROTOCOL where yet-to-be-defined JSON MESSAGES are exchanged with IBM i web services. It appears to me that the role of the web services is to perform DB I/O, including reads, writes, updates, deletes, outputs of SQL result sets, and possibly other SQL operations. If that is the case, then I don't see much of a role for COBOL programs. I would suggest just having a UTILITY perform DB I/O for SPA clients, via a messaging protocol, where messages are authorized and validated, which protects against SQL injection from browsers, and ensures that only certain users and user groups are authorized to the DB resources requested. The UTILITY should just perform DB I/O and SQL operations against "requested" tables and SQL views, and return results, including error messages. Is that right?
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.