Mark Lobue wrote: > > Check out "Network Programming with Perl". It can show you how to set up > an easy client-server system, where your mail server can call the client, > and > the client contacts the server through a socket. Even if many clients > fire at once, the socket connection forces serialization of the requests, > and ensures you will have enough time to determine if the IP is a > duplicate. The multiple clients will have to wait in turn for the socket > to be available, but at the same time, will free up your mail server to > move on to other tasks. >
what happen if the first connection queue up and the server decided to spawn another thread (process) to server the next connection? the first connection arrives first but it's queued up so the server decided to serve the rest of the connection. if you only have a serial server, this technique will work well but i don't see many server implementation that only serve one client at a time this day. i haven't follow this thread closely so i could have miss something along that way. if no, please feel free to ignore my post. if you only have a single machine(ie, not a server farm or anything like that), check out the share memory technique which is faster than writing lock file. dvaid -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
