Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 13623 invoked by uid 500); 27 Nov 2002 15:26:15 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 13398 invoked from network); 27 Nov 2002 15:26:10 -0000 Message-ID: From: Juan Rivera To: "'dev@httpd.apache.org'" Subject: Request for comments: Managing max connections per protocol Date: Wed, 27 Nov 2002 10:19:05 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/mixed; boundary="----=_NextPartTM-000-cb619f57-0215-11d7-8236-00508bc5d7ff" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------=_NextPartTM-000-cb619f57-0215-11d7-8236-00508bc5d7ff Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C29628.53030400" ------_=_NextPart_001_01C29628.53030400 Content-Type: text/plain One of the missing pieces in Apache 2 to support multiple protocols is the ability to limit the number of connections per protocol. Right now you specify the max number of connections but there is no way to manage how many connections a particular protocol can manage. Anyways, the problem seems like that by the time the protocol handler decides it will process the request, it is too late for the core to do anything. Now, if we add an extra optional hook to the protocol handlers that manages the max connections for the protocol bypassing the core functionality. It will be up to the protocol handler to write the code that enforces a maximum number of connections. I though that the core could do that if the extra hook just tells the core that the module will manage the request. The problem I see with this approach is that if protocol handlers need some complex way to manage how many concurrent connections are handled, this model will not satisfy that. Comments? _____ Juan C. Rivera Citrix Systems, Inc Tel: (954)229-6391 ------_=_NextPart_001_01C29628.53030400 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

One of the missing pieces in Apache 2 to support multiple protocols is the = ability to limit the number of connections per = protocol.

 

Right now you specify the max number of connections but there is no way to = manage how many connections a particular protocol can = manage.

 

Anyways, the problem seems like that by the time the protocol handler decides it = will process the request, it is too late for the = core to do anything.

 

Now, if we add an extra optional hook to the protocol handlers that manages = the max connections for the protocol bypassing the core functionality. It will = be up to the protocol handler to write the code that enforces a maximum number = of connections.

 

I though that the core could do that if the extra hook just tells the = core that the module will manage the request. The problem I see with this approach is = that if protocol handlers need some complex way to manage how many concurrent connections are handled, this model will not satisfy = that.

 

Comments?

 

 

Juan C. Rivera

 

Citrix Systems, Inc

 

Tel: (954)229-6391

 

------_=_NextPart_001_01C29628.53030400-- ------=_NextPartTM-000-cb619f57-0215-11d7-8236-00508bc5d7ff--