> > > You could run a small pool > > > (1 or more) of processes each of which handles multiple concurrent > > > smtpd connections. > > > > Sorry, sort of beginner programmer question, to be clear > > what you say, concurrent connections would be handled by > > a policy server by spawning a new thread when a new connection > > is made? I can see this could solve problem if all threads see > > the same DB connection. > > No, I was thinking non-blocking event-based concurrency in a single > thread.
Hmm sounds impossible - how can single thread do more than one thing at a time? Guess I have some google-ing to do, learn how single thread could use events to handle more than one request at same time. > How about just testing the simplest implementation first though. > Just use spawn, with one database connection per process and > see how that goes. Already doing that. :) Just trying to learn for the next step :) Thank you for your help.
