Hi, You can create a daemon is several ways, but here are two of them: 1. Create non blocking sockets for the server, and on every new communication open a new thread that will use that connection. 2. Create a non blocking sockets for the server, and on every new communication open a new process that will handle that connection.
I suggest that you open things by need, rather then by demand, because you never know how much connections you'll need, and if you'll only need one, and you will have 10, then it's "too much" for what you need. Ido On 6/2/07, Francisco Reyes <[EMAIL PROTECTED]> wrote:
After reading the socket samples at http://www.bastisoft.de/pascal/pasinet.html I am starting to get the basics of socket programming. The one thing I don't see in that page is how one would have standby servers. In other words I would like my server program to have some N number of daemons to handle the connection. Like one can do with apache.. Have a minimun number or processes always running with the ability to grow as needed up to a maximun number of processes. I don't have exact numbers, but my guestimate is that during the busiest times of the day the program will need to handle 5 to 10 connections per second.
-- http://ik.homelinux.org/ _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
