poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13478] - [RFE] POIFS, RawDataBlock: Missing workaround for low performance InputStreams
Date Tue, 18 Mar 2003 19:28:04 GMT
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=13478>.
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=13478

[RFE] POIFS, RawDataBlock: Missing workaround for low performance InputStreams

sys@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From sys@yahoo.com  2003-03-18 19:28 -------
I disagree with the above solution.

BufferedInputStream does not work because it is also not guaranteed to return
512 bytes on each read (what RawDataBlock excepts).

The above solution remedies the situation by providing the user with an 
alternate InputStream that that guarantees it is able to return the properly 
sized block of data. The BlockingInputStream supplied, does not time out.

I feel the real problem is that RawDataBlock should be more tolerant in it's 
use of InputStreams. RawDataBlock should repeat reads until the desired chuck 
of data base been read. If too many failed reads, then RawDataBlock should 
throw error as it does now.

I have attached above my proposed solution. Patch file and RawDataBlock.java

Mime
View raw message