Chris,
This is _so_ helpful.
On 12/11/20 3:00 PM, Christopher Schultz wrote:
Rob,
On 12/11/20 15:00, Rob Sargent wrote:
> [huge snip]
Your “Job” example seems along the lines of get-it-off-the-servlet,
which again points back to my current queue handler I think.
Yes, I think so. So let's g
Rob,
On 12/11/20 15:00, Rob Sargent wrote:
> [huge snip]
Your “Job” example seems along the lines of get-it-off-the-servlet,
which again points back to my current queue handler I think.
Yes, I think so. So let's get back to your original idea -- which I
think is a good one -- to use a shared
Chris,
Thank you for the completeness. I always miss on getting the correct detail
(too little, too much) in my postings.
> On Dec 11, 2020, at 11:31 AM, Christopher Schultz
> wrote:
>
> Rob,
>
> On 12/9/20 23:58, Rob Sargent wrote:
>> My apologies if this is too vague to warrant considerati
Rob,
On 12/9/20 23:58, Rob Sargent wrote:
My apologies if this is too vague to warrant consideration.
It is vague, but we can always ask questions :)
In the recent past I managed a naked port, a Selector, a
ThreadPoolExecutor and friends (and it worked well enough...) but a dear
and knowled
Not a problem -- that was my issue as well, I'm just not familiar with the
code, and it can take a while to figure it out.
In the meantime, we're testing with only ECC the certificate for now, but
of course it would be nice to have both.
Thanks for looking into it.
On Fri, Dec 11, 2020 at 12:56
Robert,
On 12/9/20 21:31, Robert Turner wrote:
Actually, one incorrect statement in my previous response. testssl.sh
didn't report the details of the certificate chain, only that it was
broken. I used https://ssllabs.com/ssltest/analyze.html as well, and it
reported the specific details of the c
