Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 32760 invoked from network); 9 Feb 2007 13:33:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Feb 2007 13:33:53 -0000 Received: (qmail 35921 invoked by uid 500); 9 Feb 2007 13:33:56 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 35858 invoked by uid 500); 9 Feb 2007 13:33:55 -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 35847 invoked by uid 99); 9 Feb 2007 13:33:55 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Feb 2007 05:33:55 -0800 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=RCVD_IN_NJABL_DUL X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.117.252.25] (HELO ip9.elmar.co.il) (192.117.252.25) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Feb 2007 05:33:45 -0800 Received: from netmask.it (ip9.elmar.co.il [192.168.1.9]) by ip9.elmar.co.il (8.12.1-20030917/8.12.1) with ESMTP id l19DapJs021278 for ; Fri, 9 Feb 2007 15:36:51 +0200 Sender: root@localhost.localdomain Message-ID: <45CC78F3.D3006EFB@netmask.it> Date: Fri, 09 Feb 2007 15:36:51 +0200 From: Eli Marmor Organization: Netmask (El-Mar) Internet Technologies X-Mailer: Mozilla 4.08 [Hebrew Support by elmar.co.il (X11; I; Linux 2.4.8-26mdk i686) MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: protocol module ? References: <45C34684.7050403@turner.com> <20070208002026.234a0886@grimnir> <45CB23B8.506@bellsouth.net> Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Gregory Nicholls wrote: > > I've been looking at mod-ftpd and mod-pop3 with a view to writing a > protocol module. What I haven't been able to work out from reading > these, is how a particular protocol module 'registers' its interest in > specific connections. > eg. Assume there's 2 protocols being used and we have Listen 8080 http > and Listen 1234 foo. I use ap_hook_process_connection to insert mod_foo > into the chain. So far so good but I only want to process connections > coming on port 1234. Neither mod-ftpd or mod-pop3 seem to have any code > that examines the connection with a view to declining those they can't > process. So I'm guessing that there's some mechanism for assigning > protocols/ports to a specific module. I just don't know how to do it. > Can some kind soul point out what I've missed please ? > Thanks, > Gregory Nicholls I don't know if it will help you, but Ryan Bloom dedicated a chapter for that in his book ("Using Apache to Serve Different Protocols", pp. 383-401). In addition, mod_ftpd and mod_pop3 are not the only non-httpd protocol modules, and there are some else, such as mod_smtpd. I wish there was a mod_named (or mod_dns or mod_bind, I don't care). One day, maybe I'll write one... -- Eli Marmor Netmask (El-Mar) Internet Technologies Ltd. __________________________________________________________ Tel.: +972-9-766-1020 8 Yad-Harutzim St. Fax.: +972-9-766-1314 P.O.B. 7004 Mobile: +972-50-5237338 Kfar-Saba 44641, Israel