I'd say that CGI uses profile swapping. Why else would the job user be a server account while the current user is the end-user?
I understand you don't want to divulge the specifics of your proprietary framework.
Thanks
-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Friday, December 30, 2016 10:55 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] In-house authentication & authorization
By dispatcher I mean an app whose sole purpose is to spawn processes
for new incoming requests.
Okay. That's how the IBM i HTTP CGI interface works. The main HTTP process may spawn additional CGI JOBs to handle new incoming requests, or alternatively pass requests to idle JOB instances.
But the scenario I posed, was referring to a web portal program, which submits new JOBs when users click on menu items, and using an HTTP plug-in to "route" requests to them. End-user state is maintained in each JOB. This is somewhat similar to persistent CGI. Except users have control over starting and ending JOBs. Menu item click starts the JOB, while an "Exit"
link ends the JOB and returns users to a menu.
Big questions:
1. What server language/framework are using?
2. How do get user requests to their personal job?
Our web portal and framework is delineated at:
http://www.relational-data.com/content/portal/
Our server language is ILE RPG. If you'd like to see a demo, please contact me off-list.
midrange.com
