<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 08/04/2025 13:51, Engebretson, John wrote:<br>
<blockquote type="cite" cite="mid:1cdf778b84b14eeda1bd8ee2808c6e24@amazon.com">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"> Brian, Alan, Markus, Chen – thank you for
your feedback on this issue! At this point we seem to agree
that 1) there is merit to this idea, 2) nobody loves a new
public class (including me), and 3) this is not a subclass of
ByteArrayOutputStream. Are we ready to move this to CSR and
continue the API discussion there?<o:p></o:p></p>
<p class="MsoNormal"> Thank you very much! <span style="font-family:"Segoe UI Emoji",sans-serif">
😊</span><o:p></o:p></p>
<br>
</div>
</blockquote>
I think there is agreement that
ByteArrayOutputStream.unsynchronized(int cap) (or some such method)
would be useful. It would not require using a contiguous byte[] as
the backing array so there is scope to experiment with
implementations that don't need to resize like the base BAOS does.<br>
<br>
Extending BOAS means the size is limited to an int. To go beyond
would be a different API and there is lots of scope to do
experiments. I think too early to create a CSR for MOS, assuming
this is what you mean.<br>
<br>
-Alan<br>
</body>
</html>