You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/11/12 18:59:50 UTC

DO NOT REPLY [Bug 24647] - content-length in ResourceReader

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24647>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24647

content-length in ResourceReader

joerg.heinicke@gmx.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|ResourceReader and non-     |content-length in
                   |caching pipelines           |ResourceReader



------- Additional Comments From joerg.heinicke@gmx.de  2003-11-12 17:59 -------
The problem is the streaming of the file, is it correct? You can set the
content-length header after the first PDF byte has been sent.

I don't like the idea of "doing this only for PDF". If there is another file
format needing this feature, you code it too. Making it configurable is much
cleaner IMO.

Joerg