Got it. This all makes perfect sense! Thanks Alex.
Regards,
Kashyap
On Sat, Jun 8, 2019 at 12:03 AM Alexander Burger
wrote:
> Hi Kashyap,
>
> > I see, so if app0, app1 and app2 are on different machines and say the
> > first request from the client hits app0, and app0 forks a process to
>
Hi Kashyap,
> I see, so if app0, app1 and app2 are on different machines and say the
> first request from the client hits app0, and app0 forks a process to handle
> the session with the client. I presume that the subsequent requests from
> the client would somehow be routed to app0 - correct?
Thanks Alex,
I see, so if app0, app1 and app2 are on different machines and say the
first request from the client hits app0, and app0 forks a process to handle
the session with the client. I presume that the subsequent requests from
the client would somehow be routed to app0 - correct? if so,
Hi Kashyap,
> This is the definition of loadbalancing from
> https://www.nginx.com/resources/glossary/load-balancing/
OK, that's what I thought of.
> [image: image.png]
Thanks for the nice picture :)
> This is not a static system. The argument being that the database could
> have different
Hi Alex,
This is the definition of loadbalancing from
https://www.nginx.com/resources/glossary/load-balancing/ nginx is a
popularly used as a loadbalancer - while this is an L7(application layer
from OSI) load balancer, the term loadbalancer can be used for other layers
too.
A load balancer
Hi Kashyap,
> If an OS instance can only run N picolisp processes. What would be the
> strategy to serve more than N concurrent clients?
As I said, I don't know about load balancers. But in any case it depends on the
structure of the system. Is it a static system, which can be put on several
Hi,
If an OS instance can only run N picolisp processes. What would be the
strategy to serve more than N concurrent clients?
Regards,
Kashyap
On Fri, Jun 7, 2019 at 12:12 AM Alexander Burger
wrote:
> Hi Kashyap,
>
> > If I understand correctly, picolisp web app forks a process to handle the
> >
Hi Kashyap,
> If I understand correctly, picolisp web app forks a process to handle the
> requests from a browser session. httpGate can route the subsequent requests
> from the browser to the right process.
Correct.
> How about hosting multiple instances
> of the server behind a load balancer?
Hi,
I am guilty of not having delved into the picolisp application framework
much but I'd appreciate it very much if I could get an answer to this
question.
If I understand correctly, picolisp web app forks a process to handle the
requests from a browser session. httpGate can route the subsequent
