On Mon, Nov 03, 2003 at 01:35:38PM -0800, Scott Laplante wrote: > Specifically, we would want connection threads bound to port 80, and > internal communication threads (i.e. event messages between servers in the > cluster) bound to port 8080 (or similar).
Yes, I'm pretty sure it can bind to two different ports, but what you would then need is a separate pool of connection threads for each of your two ports. I'm not sure, but I don't think AOLserver does that. You could certainly spawn off a bunch of non connection threads and use these for your server to server communication, but then you lose the automaic HTTP handling of AOLerver connection threads, which you probably don't want, since you're using connection threads right now. I'm curious, how do you do your server to server communication, using XML-RPC or something like that? -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
