oh,oh. If you're confused, then likely I am and don't know it. When I
finally realize the point of confusion, I'll come crawling back. (Would
love to un-confuse you, but I think I've proven inadequate there.)
Cheers, and thanks for all your time and help.
rjs
On 12/14/20 3:31 PM, Christoph
Rob,
Apologies for the top-post, but at this point I think (a) you are
satisfied you are on the right track and (b) I have become more
confused. Given that (a) is much more important than (b), we can just
leave it at that.
:)
Feel free to come back for further clarifications of suggestions
>>> Calling save() from the servlet would tie-up the request-processing thread
>>> until the save completes. That's where you get your 18-hour response times,
>>> which is not very HTTP-friendly.
>> Certainly don't want to pay for 18 EC2 hours of idle.
>
> So your clients spin-up an EC2 insta
Rob,
On 12/11/20 18:52, Rob Sargent wrote:
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 h
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
My apologies if this is too vague to warrant consideration.
In the recent past I managed a naked port, a Selector, a
ThreadPoolExecutor and friends (and it worked well enough...) but a dear
and knowledgeable friend suggested embedding tomcat and using http.[3]
I have that working, one request
