From modules-dev-return-851-apmail-httpd-modules-dev-archive=httpd.apache.org@httpd.apache.org Mon Jun 11 18:47:15 2007 Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@locus.apache.org Received: (qmail 22156 invoked from network); 11 Jun 2007 18:47:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Jun 2007 18:47:15 -0000 Received: (qmail 76869 invoked by uid 500); 11 Jun 2007 18:47:18 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 76839 invoked by uid 500); 11 Jun 2007 18:47:17 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 76825 invoked by uid 99); 11 Jun 2007 18:47:17 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2007 11:47:17 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2007 11:47:13 -0700 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Hxoug-0000PQ-Ue for modules-dev@httpd.apache.org; Mon, 11 Jun 2007 11:46:50 -0700 Message-ID: <11066219.post@talk.nabble.com> Date: Mon, 11 Jun 2007 11:46:50 -0700 (PDT) From: Brad Harper To: modules-dev@httpd.apache.org Subject: apache as an application platform? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: brad.harper@epsiia.com X-Virus-Checked: Checked by ClamAV on apache.org I'm attempting to scope out the amount and type of work necessary to re-implement a legacy one-off server application. It is centered around search and retrieval of content. The input is special-purpose and currently being indexed by a home-grown technology that predates lucene or any other of the OS alternatives. I'm considering use of a stripped-down apache server using domain-specific modules as the application platform, leveraging APR and pre-existing modules for security, SSL, logging, etc. The search technology would become lucene-based. The original app uses raw sockets to read a fit-to-purpose protocol and returns content with a primitive payload header. With HTTP/HTTPS as a protocol, I'm further considering re-implementation of this interface as a web-service, using XML-RPC. The original server is implemented in C++ of varying quality. The apache route seems attractive, rather than a Tomcat re-write, since the caching, thread-safety, security, etc. is largely handled by httpd. I'm hoping that much of the domain-specific logic can be re-used and moved into modules. Comments anyone? Pros? Cons? Has anyone attempted anything like this? Thanks. Brad -- View this message in context: http://www.nabble.com/apache-as-an-application-platform--tf3903240.html#a11066219 Sent from the Apache HTTP Server - Module Writers mailing list archive at Nabble.com.