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 32056 invoked from network); 24 Jan 2000 21:14:06 -0000 Received: from rubel.maz.org (209.60.53.26) by 63.211.145.10 with SMTP; 24 Jan 2000 21:14:06 -0000 Received: (qmail 10503 invoked by uid 500); 24 Jan 2000 21:16:27 -0000 Date: Mon, 24 Jan 2000 13:16:27 -0800 (PST) From: brian moseley X-Sender: bcm@rubel.maz.org To: cocoon-dev@xml.apache.org Subject: Re: servlet or no? (was Re: [Moving on] SAX vs. DOM part II) In-Reply-To: <388CBEE8.22CAD57@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 24 Jan 2000, Pierpaolo Fumagalli wrote: > Or probably you're not fond enough about HTTP, servlets > and their similarities or differences from the SMTP and > the email world to see that in most cases they cannot > coexist. unfortunately you don't know enough about my work to make that claim. as a matter of fact i am very fond of http. you persist in claiming that i am trying to rehash your decision not to implement an smtp server with servlets. i'm not. im claiming that the servlet request/response classes can be the appropriate interface for the producer/processor/serializer engine, that it doesn't need to be limited to being http-specific. to me there is a big difference between "servlets" and everything that word implies, and the simple data structures that are requests and responses.