On Mon, Mar 28, 2016, at 13:42, Hans-Christoph Steiner wrote:
> So NetCipher's ch.boye for a long time has included the ability to use a
> custom keystore. Mark and I have been thinking that this could be a
> good approach for a form of integrated pinning in the NetCipher wrappers
> for all of
So NetCipher's ch.boye for a long time has included the ability to use a
custom keystore. Mark and I have been thinking that this could be a
good approach for a form of integrated pinning in the NetCipher wrappers
for all of the various HTTP APIs (HttpURLConnection, Apache HttpClient
for
Mark Murphy:
> On Mon, Mar 28, 2016, at 07:42, Hans-Christoph Steiner wrote:
>>> To help prevent memory leaks, in case clients fail to unregister their
>>> callbacks.
>>
>> I'd prefer to error/warn the user about this rather than reducing the
>> impact of doing the wrong thing. I vaguely
On Mon, Mar 28, 2016, at 07:42, Hans-Christoph Steiner wrote:
> > To help prevent memory leaks, in case clients fail to unregister their
> > callbacks.
>
> I'd prefer to error/warn the user about this rather than reducing the
> impact of doing the wrong thing. I vaguely remember seeing such
>
Mark Murphy:
> On Fri, Mar 25, 2016, at 05:36, Hans-Christoph Steiner wrote:
>> * why did you use the custom WeakSet class rather than just a plain Set?
>
> To help prevent memory leaks, in case clients fail to unregister their
> callbacks.
I'd prefer to error/warn the user about this rather
