RE: configurable AJP Buffer Size
>>-Original Message- >>From: Mladen Turk [mailto:[EMAIL PROTECTED] >>Sent: Thursday, April 06, 2006 12:57 AM >>To: Tomcat Developers List >>Subject: Re: configurable AJP Buffer Size >> >>Henri Gomez wrote: >>> well client and server should be in phase about the buffer size and >>> the better way to accomplish that will be via AJP13 extensions (ie >>> AJP14), with connect time negociation datas like packet buffer size :) >>> >> >>Right. Extensions could contain packet size. The problem is that even >>with the custom size that size would be limited to 32K, and again >>someone will complain about that limitation ;) Possible. But, I have no idea why connector should be constraining this. - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: configurable AJP Buffer Size
>>-Original Message- >>From: Mladen Turk [mailto:[EMAIL PROTECTED] >>Sent: Wednesday, April 05, 2006 12:21 PM >>To: Tomcat Developers List >>Subject: Re: configurable AJP Buffer Size >> >>KARNATI, SRINIVASA R [AG/1000] wrote: >>> I would like to extend AJP buffer size (in org.apache.jk.common.MsgAjp) >>as a >>> configurable option. We really needed the buffer above 8 kb (because of >>> Kerberos integration.) >>> >> >>-1. >> >>Makes no sense because other side has no clue about that. I will be implementing the similar configurable option for the client-end of the connector also (for ex., for isapi_redirector, via registry setting) This gives us at least the needed flexibility of specifying the size, and also will be able to keep up with the later releases. >>If you need larger packet size make your own flavor of >>Tomcat and mod_jk or mod_proxy_ajp or isapi_redirector >>with desired maximum packet size. This will be too constraining. >>It will not be AJP1/3 >>compliant for sure. I hope there is something I can do that becomes part of the existing protocol. I am willing to spend time on that. Thanks, Srini - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
configurable AJP Buffer Size
I would like to extend AJP buffer size (in org.apache.jk.common.MsgAjp) as a configurable option. We really needed the buffer above 8 kb (because of Kerberos integration.) Here is the plan: i) maxAJPBufferSize on connector definition will accept buffer size above 8 kb For example: if maxAJPBufferSize attribute is absent, then 8 kb is the default. ii) add a new constructor to MsgAjp to take in the size parameter I appreciate any comments/suggestions in this regard. Thanks, Srini - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. -
