Right now, the implementation flushes the buffer automatically during write. We can have an option to disable autoflushing. We can leave reseting the buffer to whatever stream/writer we're writing to.
- James Brian Moseley wrote: > On Nov 3, 2007 9:03 AM, Brian Moseley <[EMAIL PROTECTED]> wrote: > >> *cheer* >> >> i had meant to suggest this a while back, but it totally slipped my >> mind. i'm *very* happy to see it land, because Cosmo can often deliver >> huge feeds. what features are missing besides xml:lang and xml:base? i >> might be able to help. > > something that needs to be considered when switching to streamed > writing - what happens if you write enough data to commit the > response, and then an error occurs? how does the error get reported to > the client? > > my first thought is to have the writer buffer each entry and only > write it out when the close entry method is called. then, at any point > before the entry is closed, allow the caller to signal an error > condition. the writer would throw away the buffered partial entry and > instead write some sort of error element to the stream. > > thoughts? >
