Return-Path: 
 <cocoon-dev-return-34602-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 25915 invoked by uid 500); 31 Dec 2002 14:54:54 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 25902 invoked from network); 31 Dec 2002 14:54:54 -0000
Date: Tue, 31 Dec 2002 15:55:14 +0100
From: Bernhard Huber <berni_huber@a1.net>
Subject: Re: [RT] Better Environment Abstraction
In-reply-to: <3E11A176.4020600@apache.org>
To: cocoon-dev@xml.apache.org
Message-id: <3E11AFD2.5060602@a1.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2)
 Gecko/20021126
References: <3E11A176.4020600@apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

hi,

<snip/>
> So, from these, I seem to think that we could
> 
> 1) add a getInputStream() to the Request
that's okay, as org.apache.cocoon.environment.http.HttpRequest does have
such a method already.

> 2) make other input features available through request attributes
that's okay, i do the same in a webmail cocoon application.
I have removed the mail generator completly, and put
XMLizable objects into the request attribute, thus other generators xsp, 
   etc. can pull the objects they need/want to display more easily,

moreover i can display the same info object in different manner
on the same page

do you plan to enhance/use the 
org.apache.cocooon.environment.commandline, or do you plan
to add a org.apache.cocoon.environment.james packages?

> 
> In case of mail
> 
> 1) the mail content goes through getInputStream()
> 2) the attachements go through Request attributes
do you think about amount of mail content envelope only, part only, or both.
do you think about putting to much mail content via input stream
if you only want to get the subject field for example?

making mail content accessible via input stream forces you
to marshall the mail content, putting mail content as object
into request attribute may be more efficient,
but perhaps your requirements are mailet/james specific/forced.

regards bernhard


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org