Re: HTML Output limits

["Milan Zdimal" <milanz@xxxxxxxxx>]

Jon,

A couple things that come to mind that might cause your application to hang:
1. Are you closing the stream after you are done reading it?
i.e)  callp close(stream);

2. Headers. If you don't specify a valid content length and a content type
the application will not know when the end of the stream has been reached.
header("Content-Type: application/octet-stream");
header("Content-Length: xxxxxxxxxx));

Milan


On 2/20/07, Jon Paris <Jon.Paris@xxxxxxxxxxxxxx> wrote:
> >> I don't know what you're referring to here.  The limit of a particular
> application?
>
> The customer is building a very large web page.  At a certain size
> (difficult to tell exactly) the browser screen just stops filling up and
> just sits there.
>
> I had them change the *FINI to a write to stream file and then display
> that
> file - it works perfectly.  It only seems to fail when the CGIDEV2 program
> is writing the output directly to the browser.
>
> I could find no mention of limits anywhere and neither can the customer -
> but I also haven't a clue what else could cause it.  If the request is
> directed to the browser it hangs.  If it is directed to a file and the
> browser retrieves the file it works just fine.
>
>
>
> Jon Paris
> Partner400
>
> www.Partner400.com
>
>
> --
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.