jeneesh wrote:PSP (PL/SQL Server Pages) screens are nothing but Procedures and packages which when executed as URL in browser generate HTML pages.
How is this related to SQL or PL/SQL?
Do you want this to be handled by database? Not very clear..Yes, everything is related and about database.
because they connect to the database with a new session each time a request is made from the browser, so will have a new database session each time.Ohh.. just read this. So you mean while navigating each redirect from page-1 to page-2 will be a new session??
ranit B wrote:Web based applications are viewed through browsers... and browsers do not hold a connection to a database. They submit requests over the HTTP protocal and await a response... and once the response has been received the request is complete. So when you use PSP to make a request (if I recall correctly, it's been a long long time since I did PSP), it makes an HTTP request that is handled by the server, creates a database session, does whatever is needed (fetches data or whatever) and then passes back a response to the browser (including the data). The database session isn't held.
But my tool will only be active for a specific session and that is fine. In that case, I can use GTT right???
My screen is not APEX but like APEX.
The procs/packages contain usage of <tt>HTP Packages</tt> and <tt>HTP.PRINT</tt> method is used to generate the HTML page.
I know it's old and outdated but that is how things are existing.
Can you tell me in web-based applications what marks the Start and End of a session?
Is it the time I hit the web-app URL and the time I close the web-app?
ranit B wrote:I guess you'll have to consider something similar to Apex... implement a logical session ID, specific to that browser session that is passed with each request, and use fixed tables to store the information related to that session, and then have something scheduled on the database to clear out old sessions after a period of time (or period of inactivity) so that other people cannot access them.
Thanks Blue, for that great explanation.
But then please advise some way to keep the log of what all changes I'm doing. So later, I can generate my web-submits from these changes (logged information).