You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "destroydestiny (via GitHub)" <gi...@apache.org> on 2023/01/30 04:13:07 UTC

[GitHub] [commons-vfs] destroydestiny commented on pull request #300: VFS-824 HttpFileSystem free Unused Resources lead to HttpClient Conn…

destroydestiny commented on PR #300:
URL: https://github.com/apache/commons-vfs/pull/300#issuecomment-1407968556

   > I need to look at this more closely over the weekend: I don't know why the HTTP providers have to be unique and different compared to all the others. Is the use of concepts in this PR backward? In the PR, the "free" code now also "closes" resources and that feels backward to me. I expect the "close" code to also "free" resources are part of closing, not the other way around. Any thoughts?
   
   I think this problem needs to be considered from the beginning. The root cause is that "free" code closes httpClient.
   Refer to org.apache.commons.vfs2.provider.http4.Http4FileSystem#doCloseCommunicationLink
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org