Re: Thinking out loud about a new RPG web framework

Thorbjørn Ravn Andersen wrote:

By having a connection for every user session you may run into a scalability problem since you require the user to log out to regain the resources allocated to that connection.

What "resources"? It's a connection to a QZRCSRVS job, limited only by the number of TCP/IP ports. You put a decent timeout on the session and it works fine. Please, give me a real world example of a situation you think would not scale.

By properly using a pool for connections you can have long session timeouts and short idle times for connection timeouts allowing you to serve more users on the same hardware.

Pooling doesn't help at all with the maximum number of users, unless you are stateless.

This naturally requires that the backend calls are stateless - all needed information is passed from the session object - which you must do anyway since this is for web users.

Some applications can be stateless, but the best performance comes from stateful applications. If you're using the browser as a replacement for 5250 applications, then you need stateful connections, otherwise performance is unacceptable.

I don't want to go into a long discussion on this particular point. If you believe that all applications must be stateless, then we have a fundamental disagreement. Most business application developers I talk to agree that some applications require statefulness, and when I'm talking about a persistent connection, it's always for that class of applications.

Joe