Ron Sigal

Hi @NicoNes, On Sunday I saw your comment about working on clarifying things first, and then changing the behavior in a later edition, but I wasn't in working mode, so...

@NicoNes, yes, I mostly agree. **Stage 1.** +1. I like that you added "(i.e inputStream.read() != -1)". I was always confused by "consumed" and "fully consumed" here and there. I...

Hey @NicoNes, re; "Am I right" Yes re: "the current semantic (without the cache concept) of getEntity() and readEntity()" I guess I don't have strong feelings about the issue. I...

As for bufferEntity() and getEntity(), if we keep the ability of getEntity() to retrieve a backing InputStream, then I think your suggestion makes sense. Otherwise, it's moot.

Hi @NicoNes, 1. I think your updated javadoc is good. I think there should also be an additional sentence or so to clarify that hasEntity() applies to either an entity...

@NicoNes, [email protected]. See https://accounts.eclipse.org/mailing-list/jaxrs-dev.

I was just reminded that my original motivation for raising https://github.com/eclipse-ee4j/jaxrs-api/issues/706 "Clarify javax.ws.rs.core.Response javadoc wrt extracting entities." was to ask for a Response.isClosed() method to make it possible to avoid...

A related (I think) issue has come up in the MicroProfile REST Client group. MP REST Client defines a class, ClientHeadersFactory, which is, essentially, a provider, and the proposed 1.4...

Also related: https://github.com/eclipse-ee4j/jaxrs-api/issues/842.

I thought about this a while ago ... given that I don't remember what I was thinking about yesterday, my recollection is a little fuzzy, but https://www.w3.org/TR/2009/WD-eventsource-20090421/#event-stream-interpretation says that an...