FW: [rt-users] (busy) function call causes browser timeout

[Todd Chapman]

You don't have to send stuff that displays. You can send HTML
comments or maybe just whitespace. You might also be able to
do some DHTML slight of hand, but I don't know how to do it.

Another option is to do the processing in the background and
return a reult page that refreshes every few seconds with a
status and finally returns the results when everything is
finished.

-Todd

On Mon, Sep 26, 2005 at 01:30:32PM -0400, Ryan von Gleich wrote:
> >
> > I assume that your init block has a loop that calls clone the number
> > > of necessary times. If that is not so, you need to refactor clone
> > > so that you can call it once for each needed clone. As long as
> > > each individual call to clone is less time than the browser timeout
> > > you will be able to send output to the browser (from the init block)
> > > to keep it happy.
> > >
> > I know this is not crucial, but is there anyway to do away with the stuff
> that is sent to the browser so that it is gone when the before function call
> is completes and sends the new page?
> Thanks Ryan