struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <mgai...@hotmail.com>
Subject RE: Few ideas related to Struts 3
Date Mon, 15 Dec 2014 23:11:50 GMT



> Date: Mon, 15 Dec 2014 16:49:32 -0600
> Subject: Re: Few ideas related to Struts 3
> From: pbenedict@apache.org
> To: dev@struts.apache.org
> 
> Why do you guys find it bad to access the raw request/response? I haven't
> found a problem doing that as a fallback. I'd like to know what you think.
MG>More than once i've had to dig out Request and Response from Struts usually to fiddle
eTag
MG>or to finagle the Response for some proprietary JSON conversion 
MG>+1 for easy access to raw Request and Response
> 
> 
> Cheers,
> Paul
MG>Can we hear from the other participants?
MG>Cheers,
MG>Martin
> 
> On Mon, Dec 15, 2014 at 10:23 AM, Ken McWilliams <ken.mcwilliams@gmail.com>
> wrote:
> >
> > +1 for the request/response wrappers. Have you had a chance to check out:
> > https://tiles.apache.org/tiles-request/   ?
> > +1 for getting rid of Strings. Could see the benefit of what you say, but
> > if you only meant getting rid of const Strings in favour of enums that
> > alone would be pretty nice.
> >
> >
> >
> > On Sun, Dec 14, 2014 at 9:22 AM, Dave Newton <davelnewton@gmail.com>
> > wrote:
> > >
> > > Lukasz Lenart wrote:
> > > >
> > > > Request/Response wrappers
> > > > Right now user can access raw Request or Response [...]
> > >
> > >
> > > Seems reasonable, although I wonder if the appearance of not being able
> > to
> > > get the raw request/response will make people run away--they're very used
> > > to doing things icky.
> > >
> > >
> > > > No more Strings
> > > > We are passing Strings all over the framework - they represents
> > > > expressions, parameters and other different things.
> > >
> > >
> > > Strings are horrible things; +bunches.
> > >
> > > Even if they're just thin wrappers, so-called "micro types" can help a
> > lot
> > > when trying to understand what's happened, and why.
> > >
> > > d.
> > >
> >
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message