[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-cocoon-dev
Subject:    RE: Request
From:       "Vadim Gritsenko" <vadim.gritsenko () verizon ! net>
Date:       2002-05-13 14:46:50
[Download RAW message or body]

> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
> 
> 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.

I say it's tradeoff to allow easy migration of HTTP-only-oriented apps
to Cocoon 2.


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

Don't you think this will bring new wave of discussions "Cocoon Request
vs HTTP Request"?


Vadim

 
> --
> 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

[prev in list] [next in list] [prev in thread] [next in thread]