Re: Re: Printing file to browser

Well, yes, but a) you didn't explicitly note the problem of not checking the return value of the call to open and b) you're wrong when you say it has to be done line-by-line -- either construct nysus tried should work (and does, on my system =)

Philosophy can be made out of anything. Or less -- Jerry A. Fodor

Comment on Re: Re: Printing file to browser Download Code

Replies are listed 'Best First'.
(bbfu) (not line-by-line) Re(3): Printing file to browser by bbfu (Curate) on Apr 03, 2001 at 00:36 UTC
You're right, it doesn't have to be printed line-by-line. But I would recommend it. The reason is that if the file is large, then the user will (usually) see what's been read and printed so far (assuming no caching, buffering, etc) if you do it line-by-line, but will have to wait until the whole file is processed if you do it as an array slurp. And, possibly, the connection might time-out durring the slurp if you're not careful. Of course, I could be totally mistaken. :-) bbfu Seasons don't fear The Reaper. Nor do the wind, the sun, and the rain. We can be like they are.	[reply]

Replies are listed 'Best First'.

(bbfu) (not line-by-line) Re(3): Printing file to browser
by bbfu (Curate) on Apr 03, 2001 at 00:36 UTC

You're right, it doesn't have to be printed line-by-line. But I would recommend it.

The reason is that if the file is large, then the user will (usually) see what's been read and printed so far (assuming no caching, buffering, etc) if you do it line-by-line, but will have to wait until the whole file is processed if you do it as an array slurp. And, possibly, the connection might time-out durring the slurp if you're not careful.

Of course, I could be totally mistaken. :-)

bbfu
Seasons don't fear The Reaper.
Nor do the wind, the sun, and the rain.
We can be like they are.

[reply]