[forgot to CC list on this email]
On 4/27/06, B Wooster <[EMAIL PROTECTED]> wrote:
> On 4/27/06, Michael Peters <[EMAIL PROTECTED]> wrote:
> > B Wooster wrote:
> ...
> > > I've seen an archived message in this list - using "headers - none",
> > > and  then print data that will now directly go to the client browser
> > > page.
> >
> > You can use this to not only print out additional HTML, but also print
> > out Javascript to update the contents.
> ...
>
> > Well, it's kind of hard to give you more ideas unless we know why you
> > don't like those other 2 and exactly why they won't give you what you're
> > after. Having said that...
>
> Oh, I'm fine with headers-none, but not sure if there was any "better"
> or prefered way. That's all....

Found one more reason why I thought header_type('none') usage may run
into conflict - the doc has this paragraph - but how can I not use
print to display new lines ("done step1, done step2, etc") to the web
page?

>From docs:
IMPORTANT NOTE ABOUT RUN MODE METHODS

Your application should *NEVER* print() to STDOUT. Using print() to
send output to STDOUT (including HTTP headers) is exclusively the
domain of the inherited run() method. Breaking this rule is a common
source of errors. If your program is erroneously sending content
before your HTTP header, you are probably breaking this rule.

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[email protected]/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to