Tyler MacDonald wrote:
Tyler MacDonald <[EMAIL PROTECTED]> wrote:I'm working on a raw tcp/ip handler which is going to have to do nonblocking I/O. I'd like to get direct access to the apr_socket_t from the request_rec/conn_rec...OK, I found this in mod_proxy: apr_socket_t *client_socket = ap_get_module_config(r->connection->conn_config, &core_module); But that is only avaialable if CORE_PRIVATE is defined... Does that mean my module needs to define CORE_PRIVATE in order to get access to an apr_socket_t? That seems dirty to me... is there some better way?
In httpd 2.0 there's no assurance that httpd is even accessed by a socket, so of course you are rolling the dice. For example, in mod_perchild, the backend is a domain socket to another instance of Apache. In mod_ftp you would see the data socket, not the control socket, etc. It's private for a reason, if you know what you are doing, declare CORE_PRIVATE and use it. Bill
