Hi Peter, I've done some more testing here and figured out that there is a difference between the Apache and IIS webserver.
All my testings were on the Apache in the past. I moved the test csp file to a machine with IIS and it worked! Regards Alexander Riemer BEWIDATA "Peter Cooper" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > Hmmm > > I have come across something where I need to do the same thing..... > > I first tried this as a cls > Class Test.test Extends %CSP.Page [ ProcedureBlock ] > { > ClassMethod OnPage() As %Status > { > &html<<html> > <head> > </head> > <body>> > > write !,"hello "_$zh_"<br />",*-3 > hang 0.5 > > write !,"hello "_$zh_"<br />",*-3 > hang 0.5 > > write !,"hello "_$zh_"<br />",*-3 > hang 0.5 > > > &html<</body> > </html>> > Quit $$$OK > } > > } > > and it worked as expected - each line popped up with a .5 sec delay !! > ======== > > then looked at the %response.Flush() and all it does is > write *-3 > ======== > > So what problems are you seeing??? > > I can think of one - namely if you are in a table then the browsers > generally have to wait for the closing tag </table> to work out the > width of the thing > so the browser does not display anything untill it gets it all > > I actually confirmed this - just putting the same code in a table - > the browser did not display anything until the end > > ======= > if you have a block of lines - rather than write *-3 at the end you > can turn it on with > use $i:(::"+Q") > > and at the end > use $i:(::"-Q") > > Basically my issue is that I want to make a system call to > $System.OBJ.Export > and get the output on the browser line by line - rather then in a > block all at once > it works fine - but I am not in a table !! > > Peter > > > Peter > > > > > > > > On Mon, 26 Jul 2004 09:17:22 +0200, "Alexander Riemer" > <[EMAIL PROTECTED]> wrote: > >>Hi NG, >> >>I wanted to create a progress bar with CSP like >>described here: >>http://www.myblogroll.com/Articles/progressbar/ >> >>Here %response.Flush() is used massively. But I >>found out that it only works with the built in Cach� >>webserver (Port 1972). In other cases the browser >>does nothing and waits all the period until the last >>byte is sent by Cach� and then presents the progress >>bar at 100%. >> >>What's wrong? >> >>Regards >>Alexander Riemer >>Software developer >>BEWIDATA >>Unternehmensberatung und EDV-Service GmbH >>f�r den deutschen Einzelhandel >>Erthalstra�e 1 >>D-55118 Mainz >> >>Phone: +49 6131 6392-0 >>Fax: +49 6131 6392-67 >>www: http://www.bewidata.de >> >
