> On Aug 19, 2016, at 11:56 AM, Bill Cole > <postfixlists-070...@billmail.scconsult.com> wrote: > > So, is this policy server listening on port 1234 or port 7777? > I'll assume this is just inconsistent (and pointless) obfuscation...
Just a pointless obfuscation. Sorry about this. > As Wietse noted more tersely, the only way to handle concurrent connections > is to not block your ability to accept and handle a new connection while you > wait for the completion of anything that might take time with an existing > connection. You have to hand off a new connection to a new thread or process > without reading from it or writing to it, and get back to accepting new > connections as quickly as possible. I'm not fluent in Python and haven't > worked with network server code in any language for decades, so I can't say > specifically what you need to do in your program, but I know for sure that > trying to serialize your transactions in a single threaded design is > unworkable. Got your point. I'm working on fix this programming issue. Thank you very much, Bill. :)
