Differences between revisions 3 and 4
Revision 3 as of 2006-01-23 19:33:09
Size: 717
Comment: enhance doc on CommonsHTTPSender
Revision 4 as of 2009-09-20 22:48:03
Size: 718
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
A: The [http://ietf.org/rfc/rfc2616.txt HTTP 1.1 specification] makes mention of a Keep-Alive header to minimize the overhead associated with opening and closing HTTP connections. A: The [[http://ietf.org/rfc/rfc2616.txt|HTTP 1.1 specification]] makes mention of a Keep-Alive header to minimize the overhead associated with opening and closing HTTP connections.
Line 8: Line 8:
Users wishing to use the {{{Keep-Alive}}} header should use the {{{CommonsHTTPSender}}} (see Self:FrontPage/Axis/AxisCommonsHTTP). Http keep-alive is the default behavior of Commons``HTTP``Sender : there is no special configuration nor coding instruction to add. Users wishing to use the {{{Keep-Alive}}} header should use the {{{CommonsHTTPSender}}} (see [[FrontPage/Axis/AxisCommonsHTTP]]). Http keep-alive is the default behavior of Commons``HTTP``Sender : there is no special configuration nor coding instruction to add.

Q: Does Axis support the HTTP 1.1 Keep-Alive header?

A: The HTTP 1.1 specification makes mention of a Keep-Alive header to minimize the overhead associated with opening and closing HTTP connections.

In practice, the Keep-Alive feature is not particularly valuable in a corporate setting because of proxy servers.

Users wishing to use the Keep-Alive header should use the CommonsHTTPSender (see FrontPage/Axis/AxisCommonsHTTP). Http keep-alive is the default behavior of CommonsHTTPSender : there is no special configuration nor coding instruction to add.

Related topic: http://issues.apache.org/bugzilla/show_bug.cgi?id=16522

FrontPage/Axis/KeepAlive (last edited 2009-09-20 22:48:03 by localhost)