I think I want to simplify some things.
Normally, client/server async is implemented by the client/server framework.
What happens is the interchange of messages between the client and server
through the http connection on the socket is made non-blocking. But the entire
request/response still ha
Thank you so much Didier for your detailed response! I will need some time
to digest it but a lot of what you write sounds very reasonable.
Thanks!
Brjánn
On 15 May 2018 at 02:57, Didier wrote:
> Oh, I forgot something important.
>
> If you're hoping to have multiple hosts, and run this applic
Oh, I forgot something important.
If you're hoping to have multiple hosts, and run this application in a
distributed way, you really should not do this that way. Things get a lot
more complicated. The problem is, your request queue is local to a host. So
if the client creates the Future on S1 o
Its hard to answer without additional detail.
I'll make some assumptions, and answer assuming those are true:
1) I assume your S1 API is blocking, and that each request to it is handled
on its own thread, and that those threads come form a fixed size thread
pool with a size of 30.
2) I assume
Hi Oliy,
I really appreciate your input since I'm totally new to writing
asynchronous tasks. If I understand you correctly, promises are a better
way to go if only one value is collected from S2 by S1. However, S1 will
keep polling S2 (once every 1.5 secs, by S2's API specification) for
updates on
Hi,
Not a direct answer, but something that may help you simplify your problem:
I have a general rule to avoid core.async when only one value would ever be
sent down the channel. For these use cases promises are an order of
magnitude simpler, giving you control of the thread of operation, simpl
Hi!
I'm writing a server-side (S1) function that initiates an action on another
server (S2) and regularly checks if the action has finished
(failed/completed). It should also be possible for a client to ask S1 for
the status of the action performed by S2.
My idea is to create an uid on S1 that re
