Following up on MemoryOutputStream, etc. – the conversation has considered a 
few alternatives:

1. Hide the new class behind ByteArrayOutputStream.unsynchronized()
2. Create a new public class providing views to OutputStream, Channel, 
InputStream
3. Something to do with an Object[] variant

  I would personally reject any code review that used “unsynchronized()” to 
describe this class, since that is only a minor property of the change.  I 
could live with “scalable” or something along those lines.
  A new public class provides more capabilities than I initially proposed, but 
of course requires a new public class.  😊
  The Object[] variant is interesting but I have no pressing need for it.  This 
probably gets a pin in it unless someone provides a use case.

    Thoughts appreciated.  Thanks!
      John


Reply via email to