Progress bars in Inet procedures? (OpenInsight Specific)
At 31 AUG 2000 05:22:21PM Dan wrote:
Could anyone suggest any material I could look into find out how to create a progress bar during an INET_RLIST procedure call?
Thanks in advance!
Dan.
At 02 SEP 2000 12:23AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Dan,
Well one theory of how to do this ( we did do something similar for a client but didn't use INET_RLIST - we used a custom routine as INET_RLIST has several drawbacks )…
During report processing write out the progress of your report to a record in a file and have an INET procedure check that record to see how far along you are. The INET procedure could then return an HTML page reporting the status from the the user and then automatically call itself from the browser to get the next status update.
The tricky bit would be getting INET_RLIST to report it's status but it uses a callback function called WEB_RLIST_CALLBACK that the RLIST processor calls for every line of data it needs to format. I'm not sure if the source to this is available in WORKS yet but if not you could shell WEB_RLIST_CALLBACK to trap the progress instead.
[/i]World leaders in all things RevSoft[/i]
—————————–7d02ae2420276–
At 04 SEP 2000 12:51AM DAN wrote:
Thanks for your suggestions, I will look into this further…
One of the reason for adding a progress bar is that my server has a tendency to time-out if an rlist command is requesting a very large report
When it times out is this OI or is it due to my webserver?
-Dan.
At 04 SEP 2000 09:01AM Don Bakke wrote:
Dan,
My guess is that it is your web server, but you could easily establish that if you have physical contact with your web server. Just see if OEngine is still processing or not.
Sprezz's S/Web product (coupled with their S/List for the web) might be a very valuable tool for you. With this you can choose between AREV or OI as your database engine of choice. AREV, I believe, is the preferred tool of Sprezz since it is more robust than OI.
Another suggestion (regardless of whether you use OICGI or S/Web) is to pass off any "large" requests like this to a dedicated processor. Your INET procedure sends back an immediate reply indicating that their report is being processed. You can either send them the link at that time and/or have an email automatically sent with the link when the report is completed. If you send them the link immediately you could have the report processor send regular HTML status updates to that link and then replace everything with your report when completed.
At 04 SEP 2000 01:23PM [email protected] wrote:
Don,
With this you can choose between AREV or OI as your database engine of choice. AREV, I believe, is the preferred tool of Sprezz since it is more robust than OI.
Robust?? Let's hear it for OI-32bit !!
[email protected] onmouseover=window.status=imagine … ;return(true)"
Ray Chan ~ Symmetry Info
At 05 SEP 2000 12:53PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site';return(true)]The Sprezzatura Group[/url] wrote:
Dan,
One of the reason for adding a progress bar is that my server has a tendency to time-out if an rlist command is requesting a very large report When it times out is this OI or is it due to my webserver?
Well we found that Rlist re-executed the select between every page so don't expect it to be very fast… what's the exect timeout message you get? I expect it's probably OICGI returning a timeout ( 1 minute I think.. )
World Leaders in all things RevSoft
At 05 SEP 2000 08:14PM Dan wrote:
Don,
]]Another suggestion (regardless of whether you use OICGI or S/Web) ]]is to pass off any "large" requests like this to a dedicated ]]processor.
I am not quite sure how to establish the connection between 2 servers that could talk OI to one another-could you explain a little further?
I am getting a consistent
"Request timed-out" message sent back to the web browser after roughly 1 min. I notice that even though the message indicates that it times out, the file is written to completion. I would like to intercept this message (?) if possible but I can't seem to to bring up any html pages until the report has finished writing to the file.
-Dan
At 05 SEP 2000 09:34PM Don Bakke wrote:
Dan,
]]Another suggestion (regardless of whether you use OICGI or S/Web) ]]is to pass off any "large" requests like this to a dedicated ]]processor. I am not quite sure how to establish the connection between 2 servers that could talk OI to one another-could you explain a little further?
Your INET routine can simply write a record with a date/time stamp in it to a file that another machine is designed to monitor. This other machine basically loops looking for new entries. Once it finds one it reads all the necessary information from this record and processes the report. In this sense it is working like a regular workstation on the LAN.
When completed (i.e. a completed HTML-based report has been written to the web server) this same machine can send an email to the requester. An enhancement would be for the same process to write a status report in HTML so the requester can monitor that progress.
At 06 SEP 2000 04:04PM Wilhelm Schmitt wrote:
Dan,
Even after the server reports timeout, OI keeps processing the request. In the meantime OICGI won't respond to other requests waiting behind in the queue.
You can type STOP at the OI system monitor to interrupt, but we haven't found any solution for the remote client, to cancel the process.
*) For large (or otherwise time-consuming) selection processes, Don's suggestion to pass the selection process to another workstation (LAN) is a good workaround.
*) If your problem is a web-client clicking several times on the same button or link that triggers the selection process, you could also include a confirmation from within your HTML code (=Javascript's CONFIRM() function).