https://issues.apache.org/bugzilla/show_bug.cgi?id=44494
--- Comment #17 from Filip Hanik <[EMAIL PROTECTED]> 2008-03-21 08:48:11 PST --- (In reply to comment #15) > Remy and Filip, thank you for immediate checks. > > Yes, the logic is same in all of them. > > (In reply to comment #11, #12) > > I tested the patch on 5.5 and it didn't work, I will look deeper into it > > I also tested the trunk patch, and couldn't get it to work properly > > I'm sorry, I might have made a mistake in something. > I will check them more. > > (In reply to comment #14) > > if we are streaming a few megabytes of data, tomcat would have to cache all > > that data in order to support mark properly. > > If it says more in detail, > Tomcat would have to cache data only after the mark() method calling, and > Tomcat would have to cache characters up to only the size > that the application specified with the method. yes, only after mark has been called, but if you set a readAheadLimit of 10MB, one has to cache that. > > Of course, we can choose to support these methods or not to support. > I think it's wonderful if Tomcat can support that. yes, it's not a question about supporting or not supporting, it's where in the code you support that. with the bytechunk/charchunk the byte arrays referenced left and right, it makes it so much harder. I'll create a little POC to show how simpl it it is > And I'm believing that the implementation of Tomcat has enough possibility. > goes against the KISS principle :) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
