Re: Thinking out loud about a new RPG web framework

Thorbjørn Ravn Andersen wrote:

I did not advocate against stateful designs. I advocated against having statefulness more than one place, and you said that I could not create an application which could page the result of an arbitrary SQL command without recreating the query every time. Hence this is what I am looking at creating a proof-of-concept for.

Ah. Well, I advocate for having all the state in the QZCRSRVS job, and it's purely opinion as to which is best. As long as you're not imposing a restriction of statelessness, then it's up to the designer where the satte should be kept. Me, I like it with my business logic, on the server, in the QZRCSRVS job.

Or the database would be smart enough to keep the query active and allow the resultset to navigate. This is currently what I expect the i to be able to.

Again, we're arguing the same thing. If you are allowing stateful connections, then it doesn't matter to me how you do it. I prefer business logic, you prefer resultsets. Since it's fundamentally the same architecture, which is best depends on the application.

Joe