painful when we just have the port number.
OK, so again care to suggest the API definitions?
I think apr_connect() is good the way it is.
For apr_bind(), I see it looking like apr_connect():
apr_status_t apr_bind(apr_socket_t *, apr_sockaddr_t *);
Why?
This makes sense
David Reid [EMAIL PROTECTED] writes:
[OK, I'm getting better at this Reply To All stuff...]
I still haven't gotten the hang of it :( Maybe I need to study the
GNUS manual to figure out how to avoid editing the cc line to keep me
out of it.
1. Modify connect to take an apr_sockaddr_t
number parameter? That would build the complete
sockaddr for us.
OK. Care to suggest the definition?
apr_status_t apr_getaddrinfo(apr_sockaddr_t *sa,
const char *hostname,
apr_int32_t family,
apr_port_t
