Hello,
I have a simple Perl module (source code at the bottom),
which sends a string to clients connecting to port 843.
It works ok, but I'd like to rewrite it in C because
it seems to use 20m for this simple task at my
CentOS 5.5/64 Linux with httpd-2.2.3-43 and mod_perl-2.0.4:
PID USER
On Fri, Oct 22, 2010 at 23:08, Alexander Farber
wrote:
> Unfortunately there aren't many example for the protocol handlers
> on the web or in Nick's book. I've come up with the following,
> but don't know how to get the client socket via conn_rec?
apr_socket_t *client = ap_get_module_config(conn
Hi Ben,
On Fri, Oct 22, 2010 at 11:54 PM, Ben Noordhuis wrote:
> On Fri, Oct 22, 2010 at 23:08, Alexander Farber
> wrote:
>> but don't know how to get the client socket via conn_rec?
>
> apr_socket_t *client = ap_get_module_config(conn->conn_config, &core_module);
>
> But note that in most case
On Sat, Oct 23, 2010 at 00:01, Mike Meyer
wrote:
> I use that to get the socket so I can poll for it to have data in it,
> and do other things while I'm waiting. Is there a better alternative
> for that, or is this an exception?
You could do it through apr_bucket_read(APR_NONBLOCK_READ) but polli
On Sat, Oct 23, 2010 at 00:15, Alexander Farber
wrote:
> Should I maybe try
> apr_socket_t *socket = conn->cs->desc->s
> or something similar instead?
Probably not, the conn_config solution is most portable across Apache versions.
> And what do you mean by &core_module
> in my case (source code
Hello Ben and others
On Sat, Oct 23, 2010 at 12:52 AM, Ben Noordhuis wrote:
> On Sat, Oct 23, 2010 at 00:15, Alexander Farber
> the conn_config solution is most portable across Apache versions.
>
>> And what do you mean by &core_module
>> in my case (source code below)?
>
> That's the reference t
