[GitHub] httpcomponents-core issue #49: HeaderGroup uses a ReadWriteLock for access t...

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] httpcomponents-core issue #49: HeaderGroup uses a ReadWriteLock for access t...

cakofony
Github user ok2c commented on the issue:

    https://github.com/apache/httpcomponents-core/pull/49
 
    @cakofony HttpMessage, its sub classes and their implementations were always meant to be threading unsafe / non-synchronized primarily for various reasons performance being foremost. It was a conscious design design since 4.0 which I would hate to reverse. I would like to understand the reason the message was being accessed concurrently in the first place. That should not have happened.  


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...