+1 for 2.3. IMO, we should keep up with what most people are using and
not linger in legacy specs.
David
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> It was once proposed that we "leap frog" Serlvet 2.3 and go straight to
> 2.4 for Struts 2.x. But, I continually see references to little things
> people could do better if our minimum were Servlet 2.3.
>
> Since no code has been written for Struts 2.x, it does not seem
> reasonable to hold back enhancements that we could make today, if our
> minimum platform were Servlet 2.3.
>
> Here's my +1 for moving the minimum platform to Servlet 2.3, today.
> Carpe Diem!
>
> -Ted.
>
> On Sun, 29 Aug 2004 10:47:01 -0700, Martin Cooper wrote:
> > I would be very much in favour of breaking out the multipart
> > handling properties into their own section. However, I don't really
> > want to do this now. I'd prefer to wait until we rip out the
> > multipart code into a filter, rationalise the interface, and better
> > align the implementation with Commons FileUpload. With that set of
> > changes, the specific parameters will likely change, so I'd prefer
> > to change everything at once. (This is one of my own itches that
> > has needed to wait for a Struts 2.x or higher, because of the
> > Servlets 2.3 requirement. ;)
>
> On Sun, 29 Aug 2004 20:22:57 -0500, Joe Germuska wrote:
> > 29668 is basically a statement of the problem I am facing. I guess
> > I should have looked through bugzilla. It looks as though 29824
> > proposes using setCharacterEncoding, so I don't think it would
> > compile with Servlet 2.2. (I haven't tried it yet.)
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
