Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 63600 invoked from network); 24 Jan 2000 22:39:40 -0000 Received: from rubel.maz.org (209.60.53.26) by 63.211.145.10 with SMTP; 24 Jan 2000 22:39:40 -0000 Received: (qmail 11158 invoked by uid 500); 24 Jan 2000 22:42:00 -0000 Date: Mon, 24 Jan 2000 14:42:00 -0800 (PST) From: brian moseley X-Sender: bcm@rubel.maz.org To: cocoon-dev@xml.apache.org Subject: Re: [Moving on] SAX vs. DOM part II In-Reply-To: <388CD19A.84B3A12A@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 24 Jan 2000, Pierpaolo Fumagalli wrote: > Oh yes... Totally... Perfectly agreed. A servlet does > not imply a web-server with a network connection over a > socket. What the servlet API describes is a mode of > operation that is following the HTTP model of request > response. As lwp-request emulates the same > request-response model using STDIN-STDOUT, we can apply > the same model without involving a Servlet Engine or a > Web Server, but simply constructing those requests and > response objects from command line parameters and go > from there. that's more or less what i'm also talking about. read an email message from stdin, parse it, make its headers and mime parts available in the same way http headers and content parts are available from an http servlet request, give some convenience methods for commonly used operations, etc.