Re: need to know about a concurrent server
- From: kris <raghavakrishna.j@xxxxxxxxx>
- Date: Thu, 05 Jul 2007 01:19:30 -0700
On Jul 5, 10:59 am, Sheth Raxit <raxitsheth2...@xxxxxxxxx> wrote:
On Jul 5, 9:02 am, kris <raghavakrishn...@xxxxxxxxx> wrote:> In case of concurrent servers the main server waits for a client
request and after the request comes it creates a new process to handle
the client reqeust. so that in essence each client has its own server.
that is one of the design you choose, typically using fork call (in
context of Unix/C programming)
My doubt is whether the newly created process will be able to accept
any connect request
coming from the client i.e can we have multiple accept requests on a
socket at the same time
posted by two different processes.
I would suggest better to check if your OS support threads, also there
are many design alternatives for concurrent server, (i found "Richard
Steven's UNPv1 Chapter : Client Server Design Alternatives"
v.interesting.)
-Raxit
Hi,
while the parent process is running if we pass the information
regarding the filedescriptor obtained during the socket call to a new
filedescriptor using dup2.
now when the child process comes in to execution we pass the new fd to
this is process and post an accept request.
does this mean that we are posting an accept request on the same
socket we have obtained during the first socket call.
--Krish
.
- Follow-Ups:
- Re: need to know about a concurrent server
- From: David Schwartz
- Re: need to know about a concurrent server
- References:
- need to know about a concurrent server
- From: kris
- Re: need to know about a concurrent server
- From: Sheth Raxit
- need to know about a concurrent server
- Prev by Date: Re: need to know about a concurrent server
- Next by Date: Re: Cross platform pointer to program text area?
- Previous by thread: Re: need to know about a concurrent server
- Next by thread: Re: need to know about a concurrent server
- Index(es):
Relevant Pages
|