[ZCM] [ZC] 2357/ 2 Comment "filestream_iterator and HTTP Range support"

"Collector: Zope Bugs, Features, and Patches ..." <[email protected]> Thu, 06 Sep 2007 12:29:20 -0400
Newsgroups gmane.comp.web.zope.devel.collector-monitor
Message-ID <[email protected]>
Issue #2357 Update (Comment) "filestream_iterator and HTTP Range support"
 Status Pending, Zope/feature medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/2357

==============================================================
= Comment - Entry #2 by mj on Sep 6, 2007 12:29 pm

This would require seek access to the stream, which the iterator explicitly does not have.

This is a hard requirement, especially for Acrobat Reader, as it expects the ranges it requests to be returned in the same order, and it requests chunks ordered differently from actual file location.

The only workaround is to then cache the data for ranges in memory or a temp file, which becomes much more of an engineering undertaking. 
________________________________________
= Request - Entry #1 by ingeniweb2 on Sep 6, 2007 6:05 am

We cannot use the filestream_iterator "as is" when the HTTP client provides a "Range" header (Acrobat Reader does it) , because the fsi always provides the whole file content.

Would be nice for this to have a "range" parameter in the filestream_iterator constructor.

==============================================================