Usage Of Consumecontent() Of Httpentity
Solution 1:
As @Sotirios suggested, HttpEntity.consumeContent()
is deprecated so please use EntityUtils.consume(HttpEntity)
when feasible.
Let's then broadly talk about consuming an HttpEntity
. Consuming an HttpEntity
ensures that all the resources allocated to this entity are deallocated. This means that:
- The underlying stream is released.
- If your connection is pooled, your connection object will be given back to the pool. If your connection is not pooled, the connection manager will let go the connection object in question and focus on handling other client requests.
When should one use it?
You should free connection resources the moment they are no longer needed. Consuming an HttpEntity
does exactly this for you.
Can it have side effects?
I am unaware of any side effects of consuming an HttpEntity
.
Solution 2:
As you can see in the javadoc, that method is deprecated. Don't use it. It's implementation-dependent. But it should be implemented as described:
This method is called to indicate that the content of this entity is no longer required. All entity implementations are expected to release all allocated resources as a result of this method invocation
Instead, you should be using EntityUtils.consume(HttpEntity)
which is implemented as such
publicstaticvoidconsume(final HttpEntity entity)throws IOException {
if (entity == null) {
return;
}
if (entity.isStreaming()) {
finalInputStreaminstream= entity.getContent();
if (instream != null) {
instream.close();
}
}
}
It's simply closing the underlying InputStream
if necessary.
Post a Comment for "Usage Of Consumecontent() Of Httpentity"