On 4/13/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
Martin Cooper wrote:
> Should I be quoting examples of where people have suggested enhancements to
> Commons IO that you have claimed are out of scope for that component? I seem
> to remember essentially the same discussion coming up there
Martin Cooper wrote:
Should I be quoting examples of where people have suggested enhancements to
Commons IO that you have claimed are out of scope for that component? I seem
to remember essentially the same discussion coming up there. Certain methods
_could_ be added, but were not. Why?
Scope i
On 4/12/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
>
> Martin Cooper wrote:
> >>The point is not that this code is onerous, but that it is knowledge
> >>about fileuploading that we have not encapsulated in [fileupload].
> >
> > Because it was specifically not intended to be addressed by File
Martin Cooper wrote:
The point is not that this code is onerous, but that it is knowledge
about fileuploading that we have not encapsulated in [fileupload].
Because it was specifically not intended to be addressed by FileUpload.
But that doesn't answer why it can't. This is a component to ass
On 4/11/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
>
> Martin Cooper wrote:
> > Well, they've already got Commons IO, since FileUpload depends on that,
> and
> > that has FileNameUtils.getName() to get just the file name, so do we
> really
> > need to add another method in FileUpload that ju
Martin Cooper wrote:
Well, they've already got Commons IO, since FileUpload depends on that, and
that has FileNameUtils.getName() to get just the file name, so do we really
need to add another method in FileUpload that just wraps that call?
String filename = FileNameUtils.getName(item.getName())
On 4/8/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
>
> From commons-user:
> >>True, but I noted that O'Reilly's version just added this snippet to
> >>remove any trailing / or \:
> >
> > Right. The Commons FileUpload philosophy, though, is to give you exactly
> > what the browser sent, no mor
From commons-user:
True, but I noted that O'Reilly's version just added this snippet to
remove any trailing / or \:
Right. The Commons FileUpload philosophy, though, is to give you exactly
what the browser sent, no more and no less. It's not up to FileUpload to
determine what the caller wants -
