Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
At the moment, when several threads (for instance, synchronization workers called by Android) with MTM simultaneously access a host with unknown certificate, multiple decision activities will pop up, so the user will have to do the same decision multiple times. This makes it look like the application is not working correctly.
If there's already a pending decision for a given certificate, this decision should be waited for/used instead of creating a new one.
That's an awesome idea. I've encountered that problem myself in yaxim, where the connection times out after some inactivity and a new one is opened.
I estimate that this needs a change of the
Initially I planned such an API change for the HostnameVerifier implementation, but did it another way in the end.