athanassios viennas

Not sure if this is the correct group for posting!

There is a frameset holding two frames both running php scripts.
The first frame holds a recursive process which runs for a considerable
period of time doing several php and database operations. The second frame
provides a switchboard panel (java applet) which monitors and controls the
above process using a socket connection to the first script. This
architecture is hindered by the fact that the frameset will render itself
only as soon as both-frame html sources are downloaded to the client. In the
meantime whole window is freezed. However if I sleep script execution for
the first frame, the second will display properly before the first unsleeps.
This seems not to be the case for manipulating http headers and/or server
configuration.

Separating process and panel scripts in different windows should be the last
choice for many reasons. Does someone have any thoughts on this!

Regards

peter vernout

I had a similar problem. I solved it by only loading the control script, and
start the process script from the control script, this I did in a <iframe>.

However, when I have to do the same again I would create a server
task/daemon job with no relation to the webserver and control that using
sockets instead of a process started in another browser/do***ent window.
(This can even be an php job if you prefer)

Most browsers will wait for output to complete or timeout eventually, which
could cause long running scripts to fail.

Regards,
Peter

athanassios viennas

and

<iframe>.

which

Yesterday I've noticed that having the declaration sequence in the frameset
swapped (i.e. declaring control script as "frame1" and process script as
"frame2" while it has formerly been the opposite additionally requiring
halting execution in the process frame for an estimated period required for
the applet to download and start) it finally worked. I suppose launching the
process frame from the switchboard is by far a better option which I will
scrutinize rightaway!

Special thanks for the invaluable feedback!
Regards

peter vernout

Your welcome