Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <001601c1fa8a$f2fd9360$670004c0@PC103>
Reply-To: "Nicola Ken Barozzi" <nicolaken@apache.org>
From: "Nicola Ken Barozzi" <nicolaken@apache.org>
To: <cocoon-dev@xml.apache.org>
References: <022501c1fa8a$c5cfdf10$9274558b@vgritsenkopc>
Subject: Re: Request
Date: Mon, 13 May 2002 16:32:02 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

From: "Vadim Gritsenko" <vadim.gritsenko@verizon.net>

> > From: Artur Bialecki [mailto:artur@digitalfairway.com]
> >
> > > -----Original Message-----
> > > From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> > > > From: Artur Bialecki [mailto:artur@digitalfairway.com]
> > > >
> > > >
> > > > It would be nice if there was an easy way to convert
> > > > HttpServletRequest to HttpRequest, HttpServletResponse to
> > > > HttpResponse, etc.
> > > >
> > > > Right now I can't see any easy way of doing this.
> > > > Maybe new constructors or static conversion methods
> > > > that do this would be very useful.
> > > >
> > > > What do you think ?
> > >
> > > Why this would be needed?
> > >
> >
> > If you start a new cocoon project and you're _not_ using
> > other libraries that already _extend/return_ HttpServletRequest
> > and others than you probably don't need it.
> >
> > But, if you have some request/response/cookie processing
> > libraries which were used in Cocoon1 or your JSP site
> > and you're moving to Cocoon2 and want to use these
> > from XSP, etc. you either have to rewire (If you can)
> > your libraries to use cocoon's Request, Response, etc.
> > or preform the conversion in some easy way. Since the
> > first option may not allways be feasable.
>
> Do you know that Http* objects *are* *already* available in Cocoon?
> Hence my question: why do you need wrappers if you can use original
> Http* objects?
>
> PS See PhpGenerator
>
> PPS Bear in mind that Http* objects available only in HTTP environment.

Which is a hack IMO.
If the Cocoon env interface is all one needs, why have the original HTTP one
available.

It's a *big* hole in the env facade.

However, if you make a conversion class, the facade still stands...

--
Nicola Ken Barozzi                   nicolaken@apache.org
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------


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