On 4/27/06, B Wooster <[EMAIL PROTECTED]> wrote: > On 4/27/06, Michael Peters <[EMAIL PROTECTED]> wrote: > > 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....
Currently with CGI::Application there is no better way of doing this. I have talked before about wanting CGI::Application to be able to accept a coderef as a return value from a runmode (instead of just a string of HTML). That would allow CGI::App to still send out all the headers, and then when it needs to send the results to the browser, it can just call the coderef and send its return value (or it can call the coderef repeatedly until it receives no more output - I haven't thought about it in too much detail). It would be pretty simple to add this to CGI::App, but I have never bothered to code it up and submit a working patch. This would potentially end up simplifying the CAP::Stream plugin as well... Cheers, Cees --------------------------------------------------------------------- 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]
