On Wed, Jun 9, 2021 at 12:25 AM Mark Miller <[email protected]> wrote:
> > Instead of respecting stream contracts, JavaBin is given how much to read > and it diligently works to read to that point or in some cases it’s own end > marker. > > That sounds actionable, should it be reading the available contents into an array and letting javabin work with the array instead? Or perhaps to avoid that, a javbin2 format needs a prefix/header section indicating exactly how much needs to be read to keep http2 happy? I'd guess from your comment that this currently gets into problems due to JVM version/os or client/server version mismatches changing the length of something? Haven't looked at javabin code in a long while so I'm mostly guessing... -Gus
