Issues related with server architechture
From: Rajat (myself_rajat_at_yahoo.com)
Date: 02/02/05
- Next message: Jens.Toerring_at_physik.fu-berlin.de: "Re: Interpreting st_mode"
- Previous message: Mohd Hanafiah Abdullah: "Re: C Interpreter?"
- Next in thread: Barry Margolin: "Re: Issues related with server architechture"
- Reply: Barry Margolin: "Re: Issues related with server architechture"
- Reply: Alex Fraser: "Re: Issues related with server architechture"
- Reply: Keith Wansbrough: "Re: Issues related with server architechture"
- Reply: Walter Roberson: "Re: Issues related with server architechture"
- Reply: Markus Elfring: "Re: Issues related with server architechture"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 2 Feb 2005 02:27:40 -0800
Hi all,
I am working for an server application, using TCP at transport layer.
It will be a kind of routing information management through server for
all the connected client. Means every client will interchange some
information with server time by time, and based on that information
server build a table for routing information, and further send the
require information to the clients back.
Now I have some issues related with server's architecture. Shall I go
for mutithreaded architectue, like one thread will be for main socket
for ACCEPTING the new connections, and for each new connection again
create new thread. OR there will be one thread for ACCEPTING the new
connections, and one other thread will handle all the clients
connections, using select and all.
Other than that if you have any other better idea then plz let me
know.
One more thing suppose we are SELECTING a set of sockets for
readability using select, if any one socket is ready for reading, to
find which socket is readable using a loop from MIN socket descriptor
to MAX socket descriptor is really very costly if we have a large
number of sockets to select. As well as at a perticular point of time
there may be more than one sockets will be readable, So a readable
socket having greater socket descriptor may suffer from STARVATION. Is
there any way So that we can get exactly that socket descriptor which
is ready to read.
- Next message: Jens.Toerring_at_physik.fu-berlin.de: "Re: Interpreting st_mode"
- Previous message: Mohd Hanafiah Abdullah: "Re: C Interpreter?"
- Next in thread: Barry Margolin: "Re: Issues related with server architechture"
- Reply: Barry Margolin: "Re: Issues related with server architechture"
- Reply: Alex Fraser: "Re: Issues related with server architechture"
- Reply: Keith Wansbrough: "Re: Issues related with server architechture"
- Reply: Walter Roberson: "Re: Issues related with server architechture"
- Reply: Markus Elfring: "Re: Issues related with server architechture"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|