Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Leo Sutic" <leo.sutic@inspireinfrastructure.com>
To: <cocoon-dev@xml.apache.org>
Subject: RE: Back from Germany
Date: Thu, 31 Oct 2002 09:57:58 +0100
Message-ID: <000101c280bb$9db045d0$0801a8c0@Lagrange>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3DBFCC5D.9000204@apache.org>
Importance: Normal


> From: Stefano Mazzocchi [mailto:stefano@apache.org] 
> 
> Leo Sutic wrote:
> 
> >
> > >From: Stefano Mazzocchi [mailto:stefano@apache.org]
> > >
> > >  phase 2) use blocks just for deployment. This is mostly 
> similar at 
> > >WAR files today: just package your stuff as a block and 
> deploy it on 
> > >a running Cocoon.
> >
> >
> > Stefano,
> >
> > does this imply that Cocoon will move from being a servlet 
> to becoming 
> > an integral part of the servlet container?
> 
> Hey, people, I wrote several thousands of lines of emails 
> about the subject.
> 
> I'm not doing this behind your back, it's all here on cocoon-dev 
> already, just search for 'cocoon block' or 'cob' on the mail archives.
> 
> I'm restating all this because Carsten didn't got the point 
> and Giacomo 
> and I could have the idea across.
> 
> But from your comments it seems that it's still that case.

Stefano,

1) I don't care if you do it behind my back or wherever. I like it.
   It is something I've seen as the logical conclusion for quite some 
   time. Imagine - instead of deploying a war to deploy car (cocoon 
   archives) and so on, cocoon webapps are raised to the same level 
   as normal webapps.

2) I haven't been following cocoon-dev much. Your previous discussion
   was probably completely missed by me.
 
/LS


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