I tought some time ago AJP was 'deprecated' - to be replaced with
plain HTTP and mod_proxy ?

Costin

On 10/24/05, Bill Barker <[EMAIL PROTECTED]> wrote:
>
> ----- Original Message -----
> From: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
> To: <dev@tomcat.apache.org>
> Sent: Monday, October 24, 2005 1:52 PM
> Subject: Status/Authority of AJP/1.5
>
>
> > Questions since some interesting ideas have popped up with respect to the
> > next flavor of AJP...  firstoff, who holds the AJP standard; is it the
> ASF?
> >
>
> Yes, it's entirely owned by the ASF.  It evolved from JServ, which is also
> owned by the ASF.
>
> > Second, what is the status of AJP/1.5 and where is it discussed?
> >
>
> Well, http://issues.apache.org/bugzilla/show_bug.cgi?id=37100 sort of
> wandered off-topic into this area :).  Otherwise, probably
> http://tomcat.apache.org/connectors-doc/common/ajpv13ext.html is your best
> bet.
>
> > I would like to float some various questions to not only introduce some
> > 'flush' signal, to inform the outward facing server to stop caching (if
> > it was) and push out a partial response; and I'd like to explore other
> > information that could be captured with respect to balancing.
> >
>
> By itself, client-flush wouldn't be hard to implement.
>
> > Thanks!
> >
> > Bill
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> This message is intended only for the use of the person(s) listed above as 
> the intended recipient(s), and may contain information that is PRIVILEGED and 
> CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, 
> or distribute this message or any attachment. If you received this 
> communication in error, please notify us immediately by e-mail and then 
> delete all copies of this message and any attachments.
>
> In addition you should be aware that ordinary (unencrypted) e-mail sent 
> through the Internet is not secure. Do not send confidential or sensitive 
> information, such as social security numbers, account numbers, personal 
> identification numbers and passwords, to us via ordinary (unencrypted) e-mail.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to