Scott Laplante said:
> Our internal messages among different servers in our cluster are
> currently having to wait for a free connection thread, and in times of
> high traffic, this backup causes rather critical problems.
Not sure as I haven't used custom threads yet, but this is what I would
proba
_paramlocation""
> ;# URL for auto-redirects (trailing slash)
> ns_section ns/server/${servername}/modules
> ns_paramnssock8080 ${bindir}/nssock${ext}
>
>
>
> > -Original Message-----
> > From: AOLserver Discussion
> > [mailt
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 d
: Monday, November 03, 2003 9:36 PM
> To: [EMAIL PROTECTED]
> Subject: [AOLSERVER] nsd binding to > 1 port?
>
>
> I'm interested in specifics regarding whether AOLServer can
> bind itself to
> more than one port at a time.
>
> Specifically, we would want connection
I'm interested in specifics regarding whether AOLServer can bind itself to
more than one port at a time.
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).
Our in
