From: "Michael Davey" <[EMAIL PROTECTED]> > > The lib you mention has a unified Stream which has both the reading and > > writing parts in [summarising a touch]. This is nice except that it means > > that 'XmlReadStream' does not extend java.io.InputStream. It'd be nice to > > hear some good positives for the joined version > (that is, it is unlikely that an inteligent programmer will accidentally > code asFoo() in such a way that read() fails to read the data written by > write()). > > > as I think the surprise of > > discovering the io classes don't extend Java ones would be a big negative. > > Agreed. I'm not sure the positives outweigh the negative either.
I would be -1 for not supporting InputStream and OutputStream as [io] is not there to challenge Sun's APIs. However, [io] can build on Sun's APIs, thus surely it is possible to write a decorator/new API that does the same job of uniting the input and output streams? Stephen -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
