Member ap_get_protocol (conn_rec *c)

This API or implementation and order of operations should be considered experimental and will continue to evolve in future 2.4 releases, with a corresponding minor module magic number (MMN) bump to indicate the API revision level.

Member ap_get_protocol_upgrades (conn_rec *c, request_rec *r, server_rec *s, int report_all, const apr_array_header_t **pupgrades)

This API or implementation and order of operations should be considered experimental and will continue to evolve in future 2.4 releases, with a corresponding minor module magic number (MMN) bump to indicate the API revision level.

Member ap_HOOK_protocol_get_t (const conn_rec *c)

This API or implementation and order of operations should be considered experimental and will continue to evolve in future 2.4 releases, with a corresponding minor module magic number (MMN) bump to indicate the API revision level.

Member ap_HOOK_protocol_propose_t (conn_rec *c, request_rec *r, server_rec *s, const apr_array_header_t *offers, apr_array_header_t *proposals)

This API or implementation and order of operations should be considered experimental and will continue to evolve in future 2.4 releases, with a corresponding minor module magic number (MMN) bump to indicate the API revision level.

Member ap_HOOK_protocol_switch_t (conn_rec *c, request_rec *r, server_rec *s, const char *protocol)

This API or implementation and order of operations should be considered experimental and will continue to evolve in future 2.4 releases, with a corresponding minor module magic number (MMN) bump to indicate the API revision level.

Member ap_is_allowed_protocol (conn_rec *c, request_rec *r, server_rec *s, const char *protocol)

This API or implementation and order of operations should be considered experimental and will continue to evolve in future 2.4 releases, with a corresponding minor module magic number (MMN) bump to indicate the API revision level.

Member ap_select_protocol (conn_rec *c, request_rec *r, server_rec *s, const apr_array_header_t *choices)

This API or implementation and order of operations should be considered experimental and will continue to evolve in future 2.4 releases, with a corresponding minor module magic number (MMN) bump to indicate the API revision level.

Member ap_some_auth_required (request_rec *r)

Behavior changed in 2.4.x refactoring, API no longer usable

Member ap_switch_protocol (conn_rec *c, request_rec *r, server_rec *s, const char *protocol)

This API or implementation and order of operations should be considered experimental and will continue to evolve in future 2.4 releases, with a corresponding minor module magic number (MMN) bump to indicate the API revision level.

Member APR_DECLARE (apr_status_t) apr_time_ansi_put(apr_time_t *result

Some platforms cannot toggle between blocking and nonblocking, and when passing a pipe as a standard handle to an application which does not expect it, a non-blocking stream will fluxor the client app.

Member APR_DECLARE (int) apr_strnatcmp(char const *a

*end breaks type safety; where *buf is const, *end needs to be declared as const in APR 2.0

Member APR_DECLARE (apr_status_t) apr_time_ansi_put(apr_time_t *result

Note that calling this function with two NULL files on some platforms creates an APR_FULL_BLOCK pipe, but this behavior is neither portable nor is it supported.

Passing proc as a *proc rather than **proc was an odd choice for some platforms... this should be revisited in 1.0

Member APR_DECLARE (void) apr_sleep(apr_interval_time_t t)

write_fd duplicates the proc->out stream, it's really redundant and should be replaced in the APR 1.0 API with a bitflag of which proc->in/out/err handles should be health checked.

no platform currently tests the pipes health.

Member APR_FILEPATH_NOTABOVEROOT

in APR 0.9 and 1.x, this flag's behavior is undefined if the rootpath is NULL or empty. In APR 2.0 this should be changed to imply NOTABSOLUTE if the rootpath is NULL or empty.

Member APU_DECLARE (apr_status_t) apr_xml_parse_file(apr_pool_t *p

In apr-util 0.9 and 1.x, the type arg was case insensitive. This was highly inefficient, and as of 2.x the dbm name must be provided in the correct case (lower case for all bundled providers)