On 1/31/06, Jim Gallacher <[EMAIL PROTECTED]> wrote: > I say we leave it as is (ie continue use apr_sockaddr_port_get) and > worry about it when we do some sort of comprehensive review for apache > 2.2 compatibility.
That's fine. I was only scared that there might be an attempt to revert it to the pre-apr_sockaddr_port_get way of doing things. Leaving as-is until all the 2.2 issues are worked out is probably best. At least we know that this particular problem will be quite minor to fix when that time comes. -- Deron Meranda
