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 19740 invoked from network); 24 Jan 2000 20:33:56 -0000 Received: from phoenix.webslingerz.com (balld@206.66.49.24) by 63.211.145.10 with SMTP; 24 Jan 2000 20:33:56 -0000 Received: from localhost (balld@localhost) by phoenix.webslingerZ.com (8.8.7/8.8.7) with ESMTP id PAA22510 for ; Mon, 24 Jan 2000 15:31:38 -0500 Date: Mon, 24 Jan 2000 15:31:37 -0500 (EST) From: Donald Ball To: cocoon-dev@xml.apache.org Subject: Re: servlet or no? (was Re: [Moving on] SAX vs. DOM part II) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 24 Jan 2000, brian moseley wrote: > consider this use case: procmail pipes an email message > to a command line tool. the tool creates a servlet request > out of the message and hands the request to the cocoon > engine. the engine creates a servlet response containing an > html document. the tool places the html document on > the file system and checks the file into cvs. Thought - why not just have the command line tool construct and fire off an HTTP request? That way you're not forcing your mail server and your cocoon server to coexist. Plus you keep all of the benefits of servlets (namely persistency). In general, you should be able to map most any service request to an HTTP request. It may not necessarily be the best design pattern - I don't honestly know, but it's at least worth considering. - donald