Re: Single Page Applications

I think you are suggesting that returning JSON data is not as safe and
efficient as returning the html itself. The latter is what you would be
doing in a traditional cgidev2 application, but we have dumped that method
(although it is still supported) in RNS 6.

Of course Brad can speak for himself, but I don't think he was suggesting
that one approach was safer or better than the other; just that there are
many alternatives for generating browser pages, including server-based and
client-based frameworks/techniques.

I would suggest that client-based frameworks such as Angular JS should not
entirely replace server-based frameworks. You might continue to use
server-based techniques to generate HTML reports (stream files), transform
them into PDFs, and stream either format to browser clients.

You get a much more efficient process, and a much faster development time,
if you use the data model approach (basically the JSON) with two way
binding on the visual components. Now the developer can just arrange
components on the page and bind certain elements to data model properties.

Could you be more specific about the efficiency gains and developer
productivity? Are you suggesting that client-side tools and utilities
streamline development? If so, then how?

The model gets exchanged between the client and the server, and the RPG
part of the process is now lightweight compared to some of the complicated
cgidev2 programs we used to have.

I understand that, because browser page (UI) generation is being moved from
the server to the client.

Our data grid component can do page by page loading, filtering, sorting on
huge files just as easily as a green screen subfile can.

That's good, but it doesn't sound like 2-way binding. Or is it?