Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 83363 invoked from network); 19 Sep 2007 09:54:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Sep 2007 09:54:29 -0000 Received: (qmail 69194 invoked by uid 500); 19 Sep 2007 09:54:17 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 69129 invoked by uid 500); 19 Sep 2007 09:54:17 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 69118 invoked by uid 99); 19 Sep 2007 09:54:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 02:54:17 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [194.62.232.134] (HELO mailgate2.vodafone.co.uk) (194.62.232.134) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 09:54:13 +0000 Received: from UKWCS10.vf-uk.internal.vodafone.com (ukwcs10 [10.103.2.170]) by mailgate2.vodafone.co.uk (8.13.8/8.13.8) with ESMTP id l8J9rf9T004531 for ; Wed, 19 Sep 2007 10:53:42 +0100 Received: from ukwmxc02.vf-uk.internal.vodafone.com (unverified) by UKWCS10.vf-uk.internal.vodafone.com (Clearswift SMTPRS 5.2.9) with ESMTP id for ; Wed, 19 Sep 2007 10:55:43 +0100 Received: from ukwmxr01.vf-uk.internal.vodafone.com ([195.232.229.171]) by ukwmxc02.vf-uk.internal.vodafone.com with Microsoft SMTPSVC(5.0.2195.6797); Wed, 19 Sep 2007 10:53:03 +0100 Received: from vfag-exadm03.vfag-admin.internal.vodafone.com ([195.232.207.3]) by ukwmxr01.vf-uk.internal.vodafone.com with Microsoft SMTPSVC(5.0.2195.6797); Wed, 19 Sep 2007 10:53:02 +0100 Received: from avoexs02.internal.vodafone.com ([145.230.4.135]) by vfag-exadm03.vfag-admin.internal.vodafone.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Sep 2007 10:52:19 +0100 Received: from EITO-MBX03.internal.vodafone.com ([145.230.4.11]) by avoexs02.internal.vodafone.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Sep 2007 11:47:04 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH 43415] Logging remote port. Date: Wed, 19 Sep 2007 11:47:03 +0200 Message-ID: <3B21A253728EA247A10A692547A271530213F765@EITO-MBX03.internal.vodafone.com> In-Reply-To: <46F0E80F.9030609@one.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: [PATCH 43415] Logging remote port. Thread-Index: Acf6nVmHX9moMre4SGOyGcpBGP6AzgAA2s1Q From: =?iso-8859-1?Q?Pl=FCm=2C_R=FCdiger=2C_VF-Group?= To: X-OriginalArrivalTime: 19 Sep 2007 09:47:04.0996 (UTC) FILETIME=[093C9640:01C7FAA2] X-Virus-Checked: Checked by ClamAV on apache.org > -----Urspr=FCngliche Nachricht----- > Von: Adam Hasselbalch Hansen=20 > Gesendet: Mittwoch, 19. September 2007 11:13 > An: dev@httpd.apache.org > Betreff: Re: [PATCH 43415] Logging remote port. >=20 >=20 > Pl=FCm wrote: >=20 > > 1. Please provide a patch against trunk. >=20 > mod_config_logger.c hasn't changed in trunk, so the patch=20 > will work fine. Sorry. Just a default comment if someone sends in a patch that is not against trunk :-). >=20 > > 2. Please also add a patch for the documentation. >=20 > Done. Fine, I have already seen it in the report. >=20 > > 3. I am not too happy with using %R, but to be honest I=20 > have no better proposal :-). > > Maybe other have. >=20 > Well, then... ;) I will leave around for just one or two days. If nobody has a better idea we just take %R. Feel free to bug me if your patch falls off my = radar. >=20 > > 4.=20 > >=20 > > Instead of using > > + return apr_psprintf(r->pool, "%u",=20 > r->connection->remote_addr->port); > > I would prefer > > + return pfmt(r->pool, (int) (r->connection->remote_addr->port)); > > like used for log_status. >=20 > Well, in log_server_port, apr_psprintf is used, so that's=20 > what I used.=20 > But I really don't care one way or the other. Is there a particular=20 > reason for using one or the other? I think that using pfmt is more efficient and burns less cycles than = apr_psprintf (I think this would be also the case for log_server_port), but I may be = wrong on this. Additionally pfmt checks if port is <=3D 0 and logs a "-" in this case, = but this should not be the case for r->connection->remote_addr->port, so we could use = format_integer or apr_itoa directly. Regards R=FCdiger