[jira] Issue Comment Edited: (HTTPCLIENT-696) java.util.logging configuration examples does not work as intended

[ https://issues.apache.org/jira/browse/HTTPCLIENT-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654236#action_12654236 ] mclark edited comment on HTTPCLIENT-696 at 12/7/08 12:09 PM:

[jira] Commented: (HTTPCLIENT-696) java.util.logging configuration examples does not work as intended

[ https://issues.apache.org/jira/browse/HTTPCLIENT-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654236#action_12654236 ] Michael Clark commented on HTTPCLIENT-696: -- I believe Elias's suggested fix is

Re: svn commit: r724147

Sam Berlin wrote: I'm fairly certain this change will have unintended consequences. One of the quirks about interestOps is that they are legally allowed to be set from any thread -- this is what allows a currently-blocked selector to wakeup seeing some new interestOps (when coupled with a select

Re: svn commit: r724147 - /httpcomponents/httpcore/trunk/module-nio/src/main/java/org/apache/http/impl/nio/reactor/IOSessionImpl.java

I'm fairly certain this change will have unintended consequences. One of the quirks about interestOps is that they are legally allowed to be set from any thread -- this is what allows a currently-blocked selector to wakeup seeing some new interestOps (when coupled with a selector.wakeup). The sim

Re: Certificate Validation

Partha Venkatavaradhan (pavenkat) wrote: Is it mandatory that I call Protocol.registerProtocol(). No, it is not. Because I have the following lines in my code: Protocol https = new Protocol("https", new StrictSSLProtocolSocketFactory(), port);